Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!news2.arglkargh.de!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: What's the deal with deadlocks Date: Sun, 17 Apr 2011 19:30:45 +0200 Lines: 13 Message-ID: <910me5Fr70U1@mid.individual.net> References: <23020668-d86c-489a-988b-7b379f34851c@j13g2000pro.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net clzShZ1QzNBzpI7kTYzLqg/qsfF7+m1B32oTjJ91TE+52Ra78= Cancel-Lock: sha1:zGoBNd1kh/07h7P7HNJIiUh+QEY= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 In-Reply-To: <23020668-d86c-489a-988b-7b379f34851c@j13g2000pro.googlegroups.com> Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3090 On 04/17/2011 06:15 PM, Joe Snodgrass wrote: > > The general concept is simple enough, but it seems to me that you'll > need special tools to diagnose this specific problem. How do you get > the debugger to look inside threads, see that they're hung, and find > out where the problem is happening? Do the debuggers have some > features that I haven't heard of? TIA. IIRC a simple thread dump to console will already show deadlocks. Kind regards robert