From: john AT jpsc DOT co DOT uk (John Cooper) Subject: Re: Exception number: c0000005 (access violation) 25 Jun 1997 07:33:27 -0700 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: Reply-To: john AT jpsc DOT co DOT uk Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Virtual Access by Ashmount Research Ltd, http://www.ashmount.com Original-To: john AT jpsc DOT co DOT uk Original-Cc: gnu-win32 AT cygnus DOT com In-Reply-To: <2.2.32.19970624145107.00960e44@ma.ultranet.com> Original-Sender: owner-gnu-win32 AT cygnus DOT com > >I get this sometimes at RtlFreeHeap+0x21, on program runs with the same > Your message came right after I started seeing these pop up with another > application I was extending. This application has no relation to gnu-win32 > (God forbid!;-)). It appears from the documentation that this is indicative > of a memory overwrite situation. You and I are both going to need some > memory debugging tools/gobs of time to track down our respective problems. > Although I'll make no guarantees, I don't think your problem is specifically > related to gnu-win32. I know mine is not. I think it must be b18 (or b18+Mingw32) related as I had the same program built with b17 running for several weeks of intensive testing. The only change I have made in going to b18+ming is to use time() instead of gettimeofday(). The problem is intermittent, the same run will sometimes crash, sometimes not. My client gets the same thing sometimes. I think the problem is corruption of the heap, but I can't think how to detect when it actually happens - my crash happens at the end of a long run which does thousands (millions?) of small allocations and deallocations of memory. -- John Cooper (JPSC Ltd, UK) - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".