www.delorie.com/archives/browse.cgi | search |
egor duda wrote: > > CW> Well, I don't think I can really figure out what the problem is unless I > CW> know what program make is trying to execute in the exec_command() > CW> function -- but that data doesn't show up in the stackdump. OTOH, I > CW> can't just step through the entire build waiting for the crash -- it > CW> does not appear deterministic. > > CW> Should I build dumper.exe and try the JIT functionality? would that help? > > it would be enough (and probably easier) to use JIT debugging with > gdb. adding 'error_start=x:\path\to\gdb\gdb.exe' to CYGWIN environment > variable should do. Okay, I did this -- but I got this error (instead of the 'expected' one I reported earlier): make[2]: Leaving directory `/usr/src/cygwin/obj/i686-pc-cygwin/winsup/cinstall' 0 [main] make 1640 handle_exceptions: Error while dumping state (probably corrupted stack) Signal 11 make[1]: *** [subauth] Error 139 make[1]: Leaving directory `/usr/src/cygwin/obj/i686-pc-cygwin/winsup' make: *** [all-target-winsup] Error 2 And when gdb popped up, it had no state data from the crashed process. (e.g. it was as if I'd merely typed "gdb make" ). What should I do next? --Chuck
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |