[EXTERNAL] Re: cygwin1.dll calls assert before cygwin command hangs
Lavrentiev, Anton (NIH/NLM/NCBI) [C]
Fri Mar 24 03:32:44 GMT 2023
> 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:
(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
More information about the Cygwin