Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming.threads > #1443

Re: deadlock detection

Newsgroups comp.programming.threads
Date 2013-03-26 17:18 -0700
References <1d1a06b6-7e30-4f08-9d1b-7c64d3d4daaf@googlegroups.com>
Message-ID <39d0505f-65aa-4647-ad53-894551b5a7e7@googlegroups.com> (permalink)
Subject Re: deadlock detection
From Aaron Brady <castironpi@gmail.com>

Show all headers | View raw


On Friday, March 15, 2013 5:46:13 AM UTC-5, Aaron Brady wrote:
> Hello Group,
> 
> I don't know if this is the right group for this.  Apologies in advance if I 
> cross-post someone in another group.
> 
> I have invented a deadlock detector.  The procedure is very simple and it 
> would be very useful.  It must be broken or it would exist already.
> 
> The Wikipedia article claims it's impossible [1].  Microsoft SQL rolls back 
> transactions upon discovering it [2].  Java terminates the entire process upon 
> suspecting it [3].
> 
> [1] http://en.wikipedia.org/wiki/Deadlock#Avoidance
> [2] http://msdn.microsoft.com/en-us/library/ms178104(v=sql.105).aspx
> [3] http://publib.boulder.ibm.com/infocenter/javasdk/tools/index.jsp?
topic=%2Fcom.ibm.java.doc.igaa%2F_1vg00011883cbec-11b5a842dea-7fff_1001.html
> 
> I would like to prove or disprove my method and discuss the implications: 
> article including test and comments [4] and diagram [5].
> 
> [4] http://home.comcast.net/~castironpi-misc/irc-0085%20deadlock%20detection.py
> [5] http://home.comcast.net/~castironpi-misc/irc-0085%20deadlock%20detection.png
> 
> Thanks in advance.

Hello Thread,

I'd be remiss not to pursue this idea further.  I expected it to generate much more interest than it has so far.  According to my observations, it's because it's a good idea, but somewhat demanding.

What would people need in order to make it work in their environments, in terms of proof, documentation, optimizations, and additional functionality?  Would a "Mutex-Only" version be more suitable for discussion?

Are people interested in a userland implementation?  It would require a new synchronization API function, only one I believe, which would also be applicable elsewhere.  Or is it suited to be a kernel service?  Or, is the running time just too slow just too often to ever provide for anyone?

Thanks in advance!

Back to comp.programming.threads | Previous | NextPrevious in thread | Find similar


Thread

deadlock detection Aaron Brady <castironpi@gmail.com> - 2013-03-15 03:46 -0700
  Re: deadlock detection Michael Podolsky <michael.podolsky.69@gmail.com> - 2013-03-18 22:38 -0700
    Re: deadlock detection Robert Wessel <robertwessel2@yahoo.com> - 2013-03-19 01:03 -0500
      Re: deadlock detection Michael Podolsky <michael.podolsky.69@gmail.com> - 2013-03-19 19:14 -0700
      Re: deadlock detection Aaron Brady <castironpi@gmail.com> - 2013-03-21 22:59 -0700
    Re: deadlock detection Aaron Brady <castironpi@gmail.com> - 2013-03-19 17:17 -0700
      Re: deadlock detection Michael Podolsky <michael.podolsky.69@gmail.com> - 2013-03-19 19:09 -0700
        Re: deadlock detection Aaron Brady <castironpi@gmail.com> - 2013-03-20 09:07 -0700
  Re: deadlock detection Johann Klammer <klammerj@NOSPAM.a1.net> - 2013-03-19 20:24 +0100
  Re: deadlock detection Aaron Brady <castironpi@gmail.com> - 2013-03-26 17:18 -0700

csiph-web