Path: csiph.com!x330-a1.tempe.blueboxinc.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 19 Apr 2011 12:20:57 -0500
Date: Tue, 19 Apr 2011 21:18:45 -0700
From: Patricia Shanahan <pats@acm.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.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> <Xns9ECAEFF0160FEmyfirstnameosapriee@216.196.109.131> <575d7b43-51c4-4905-ba16-15fe9b78373e@t16g2000vbi.googlegroups.com> <ioi6hl$bvq$1@news.albasani.net> <ioi731$pc3$1@dont-email.me> <913q7eFpdlU3@mid.individual.net> <7c038630-5773-4ef1-8b59-1a0d6fa9acd5@z7g2000prh.googlegroups.com>
In-Reply-To: <7c038630-5773-4ef1-8b59-1a0d6fa9acd5@z7g2000prh.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <3d-dnQbWrqjkWTDQnZ2dnUVZ_tidnZ2d@earthlink.com>
Lines: 17
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 75.8.126.96
X-Trace: sv3-Gr7GjjLWCZ2tjp3TgBHP35G0ejzqIgLDP2f1dZ6zvpSQOdmJG2x6GhA1IvFUXCS6f3/DFFD1zzxwtW3!ScnccymmxhpeUxuBqWJvZ1/nU5WuKzfD063Pn6FkpDsAxZIuezCnZAgSsWEFL3KVJHH1P7FJGUev!HHno2ieQ/1uYCOv/Bxt7jboXawH/YjR2wv82B3gQ5+s=
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2093
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3157 comp.lang.c++:4048

On 4/19/2011 2:10 PM, Joe Snodgrass wrote:
...
> You got a concurrent programming project, let's say in C++, and you're
> climbing the walls, because the results are unpredictable, the
> debugger shows nothing and the code looks fine.
...

Big error. Debuggers are just tools for collecting information. They are
neither in charge of debugging, nor responsible for doing it.
Programmers are.

Climbing the walls does not help.

Thinking, reviewing code, formulating testable hypotheses and testing
them are all far more useful.

Patricia