This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Quick testfeedback...
- To: cygwin-developers at cygwin dot com
- Subject: Re: Quick testfeedback...
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Tue, 11 Sep 2001 20:42:37 -0400
- Cc: Robert Collins <robert dot collins at itdomain dot com dot au>, jason at tishler dot net
- References: <1000248820.30279.22.camel@lifelesswks> <20010911204019.H1752@dothill.com>
- Reply-To: cygwin-developers at cygwin dot com
On Tue, Sep 11, 2001 at 08:40:19PM -0400, Jason Tishler wrote:
>Rob,
>
>On Wed, Sep 12, 2001 at 09:19:19AM +1000, Robert Collins wrote:
>> On Wed, 2001-09-12 at 01:10, Jason Tishler wrote:
>> > Also, broadcast.exe (prior to patching) GPF-ed with:
>> >
>> > The instruction at "0x6100f0cb" referenced memory at "0x00000000".
>> > The memory could not be "written".
>>
>> Was this before my bugfix commit? I had misused InterlockExchangePointer
>> rather badly, which lead to pt and sched crashing for me.
>
>My last cvs update was after your bugfix commit.
>
>> If it was after the bugfix commit, I'd like to see if we can track this
>> asap...
>
>I can reproduce it frequently but not every time. I will debug it first
>thing tomorrow morning. FYI, it seems to occur right near the end of
>the test and the test still passes.
Before you go, could you tell us what "0x6100f0cb" decodes to in your
DLL?
addr2line -e cygwin1.dll 0x6100f0cb
cgf