X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-10.6 required=5.0 	tests=BAYES_00,RCVD_IN_DNSWL_HI
X-Spam-Check-By: sourceware.org
From: "Schmidt, Oliver" <oliv.schmidt@sap.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Date: Mon, 15 Mar 2010 11:45:47 +0100
Subject: Re: Cygwin 1.7: Concurrency Issue with Shared State Initialization
Message-ID: <B10B50309DC54D45A855FD66F56015F71D7AA8CF09@DEWDFECCR03.wdf.sap.corp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com


Hi Christopher,

> Is echo being run under a bash shell?  From the command prompt?  In a
> .bat file?  Repeatedly in a loop?

I experienced it in the same scenario described in my original report:
A non-Cygwin shell calling a non-Cygwin 'gnumake -j' processing Makefiles
with rules calling Cygwin programs. Echo.exe is the most called Cygwin
program as our rules contain quite some logging stuff.

> [...] cygwin1-*.dbg.bz2 [...]
> c:\>c:\cygwin\bin\gdb /bin/echo.exe <pid>
> (gdb) bt
> (gdb) x/80x $esp
> (gdb) <just hit enter here>

Thanks for the by no means at all too detailed instructions :-)

The good news are that I was again able to reproduce the "echo hang". The
bad news are however that the debugging doesn't work.

As you gave the instructions above for the cmd prompt I presumed that <pid>
refers to the "Windows PID":

C:\>c:\cygwin\bin\gdb /bin/echo.exe 3684
GNU gdb 6.8.0.20080328-cvs (cygwin-special)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.htm=
l>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(no debugging symbols found)
Attaching to program `/bin/echo.exe', process 3684
[New thread 3684.0xe70]
[New thread 3684.0x120]
[New thread 3684.0x988]

At this point gdb "hanged" and I didn't know how to get it to bringing up t=
he
(gdb) prompt so I had to kill it.

> If it is happening in my code it will, once again, be tricky to debug
> since you actually can't attach a debugger to the process at this point
> in process initialization.

Seems we're in this situation :-(

Regards, Oliver

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple