gcj-mingw32: it compiles, it runs, it segfaults [found the culprit!]

Tue Dec 11 11:19:00 GMT 2001

Jeff Sturm <jsturm@one-point.com> writes:
> Urg. That's no help. You need to get the faulting PC somehow. On a
> Windows NT machine you could extract that from C:\WINNT\DRWATSON.LOG
> (IIRC). I have no idea what the equivalent is on Windows 98 though.

Hey, thanks everybody for your help with this. I reverted to
printf-and-commenting-stuff-out debugging mode today on my morning
BART ride and I managed to drill all the way down to where the error
is happening: System.out.println() causes the program to fail in a
really bizarre way -- just a "program aborted" -- no exceptions, no
useful information yielded by gdb. I had to trace all the way through
jvgenmain->prims->natFirstThread to find this out, though =)
I'll post more info and a fix when I have it. Suffice it to say that
it seems that all the other gcj machinery is working properly on
mingw32... at least in single threaded mode without exceptions... =)
 - a