This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cvs cygwin1.dll

On Wed, Sep 18, 2002 at 06:42:50PM +0000, Guy Harrison wrote:
>On Fri, 13 Sep 2002 08:58:16 -0400, Christopher Faylor <>
>>On Fri, Sep 13, 2002 at 09:09:37AM +0000, Guy Harrison wrote:
>>>I can't seem to figure out how to set a breakpoint in without
>>>recompiling make with debug. Any hints?
>>Just attach to the running process and set a breakpoint.
>>Alternatively, use the "dll" command to load cygwin1.dll and then set
>>a breakpoint on a *line number*.
>Thanks, the latter helped verify that debugging made the problem go away
>- ditto strace. Initially I thought it was a race. Racing certainly
>helps trigger it but that isn't the problem.
>I can't see a mechanism involving cygthread::stub to cater for the case
>where "last man out"+1 ensures "last man out" is running. In all
>situations where abnormal behaviour occurs we're left waiting upon a
>process that consists of a single suspended cygthread::stub thread.
>Others should be able to verify this by bumping up the size of the
> threads[] array up to a silly value then attempt an
>intensive configure/make/install with it. Conversely now that I've set
>threads[1] there's been no breakages.

Where are you seeing this wait?  Details please.


Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]