> Sorry, the second gdb command should be > info line *__assert+0x42a4 > > (Note the change in symbol name: two "_" there) >
I think it'd be easier to "catch" the problem rather than to chase it by running all commands under the debugger. For that, define the CYGWIN environment variable (via Windows) as: error_start=c:\cygwin64\bin\dumper.exe (that assumes that Cygwin is installed at c:\cygwin64) Then whenever the abort occurs, you'll have a core file, which can be loaded into GDB and the backtrace investigated. Something like this: $ gdb /path/to/command command.core (gdb) where My $.02, Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
