Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 11 Sep 2001 20:42:37 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Cc: Robert Collins , jason AT tishler DOT net Subject: Re: Quick testfeedback... Message-ID: <20010911204237.A919@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com, Robert Collins , jason AT tishler DOT net References: <1000248820 DOT 30279 DOT 22 DOT camel AT lifelesswks> <20010911204019 DOT H1752 AT dothill DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010911204019.H1752@dothill.com> User-Agent: Mutt/1.3.21i 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