Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: From: "Town, Brad" To: "'Earnie Boyd'" , "'Joost Kraaijeveld'" , "'cygwin AT cygwin DOT com'" Subject: RE: Exception problems-> this is a bug! Date: Tue, 28 Nov 2000 12:07:23 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com] wrote: > --- "Town, Brad" wrote: > > I compiled using "g++ -g test.cc", and I'm seeing the > behavior that Joost > > mentioned. gdb caught the exception and is currently pointing at an > > assembly instruction between the last brace of the for loop > and the last > > brace of the try block: "mov (%edx),%ecx". > > > > I did have to tweak the source a bit to get it to run. On > my machine, I got > > the message "couldn't dynamically determine load address for > > 'CharToOemBuffA' (handle 0x0), Win32 error 127". Putting a > Sleep between > > the two calls to CreateThread allows the program to run. > Looks like the > > assembly in autoload.cc needs to be thread-safe (just like > the FIXME above > > it says). > > > > Well you went so far as to find where the bug is, why don't > you supply the > FIXME for it? Why don't I? Well, it's probably because I don't have any experience with regular gcc assembly, much less making gcc assembly thread-safe. And if it's a compiler issue, forget it. I apologize for not completely solving the problem, but I believed that, given a little more information about the problem, others might be willing to help, too. Brad Town -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com