Path: csiph.com!x330-a1.tempe.blueboxinc.net!feeder1.hal-mli.net!nx01.iad01.newshosting.com!newshosting.com!198.186.194.249.MISMATCH!transit3.readnews.com!news-out.readnews.com!postnews7.readnews.com!news.uslec.net!not-for-mail
Date: Mon, 18 Apr 2011 16:59:36 -0700
From: Noah Roberts <dont@email.me>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
Newsgroups: comp.lang.java.programmer,comp.lang.c++
Subject: Re: What's the deal with deadlocks
References: <23020668-d86c-489a-988b-7b379f34851c@j13g2000pro.googlegroups.com>
In-Reply-To: <23020668-d86c-489a-988b-7b379f34851c@j13g2000pro.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 14
Message-ID: <4dacd054$0$21868$cc2e38e6@news.uslec.net>
Organization: USLEC
NNTP-Posting-Host: bed7d501.news.uslec.net
X-Trace: DXC=c`4VkTQ5;2Kj`=i9@XM8YEG3V[U]m4JkLfl=1Gg_WV;MGO7:CX?@HFK2_L8S2V6eWCTN<THLbicLH
X-Complaints-To: abuse@uslec.net
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3123 comp.lang.c++:3993

On 2011-04-17 09:15, 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.

I myself have always wondered how they could stand the smell.

It's GOT to itch like a mother too.

-- 
http://crazycpp.wordpress.com