Path: csiph.com!news.mixmin.net!aioe.org!NBiuIU74OKL7NpIOsbuNjQ.user.gioia.aioe.org.POSTED!not-for-mail From: "Chris M. Thomasson" Newsgroups: comp.programming.threads,comp.lang.c++ Subject: Re: More precision about my new inventions of scalable algorithms.. Date: Thu, 25 Feb 2021 01:05:19 -0800 Organization: Aioe.org NNTP Server Lines: 11 Message-ID: References: <1rxYH.126875$gb5.90507@fx10.iad> NNTP-Posting-Host: NBiuIU74OKL7NpIOsbuNjQ.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 X-Notice: Filtered by postfilter v. 0.9.2 Content-Language: en-US Xref: csiph.com comp.programming.threads:6361 comp.lang.c++:78561 On 2/25/2021 12:49 AM, Bonita Montero wrote: >> Think of a "master" process, than can kill a process while its holding >> a process-wide mutex. This can be handled and corrected, the state can >> be repaired into a consistent state. Its tricky, yet can be done. Wrt >> Windows think of the WAIT_ABANDONDED state. POSIX has it with EOWNERDEAD. > > If you have shared memory modified while holding the lock there's > nothing to fix. have you ever had to encounter and deal with EOWNERDEAD, or WAIT_ABANDONDED ?