issues debugging crash in cygwin dll with gdb

Wed Jul 2 10:35:45 GMT 2025

On Jul 1 16:14, Jeremy Drake via Cygwin wrote:
> I had an issue in some code I was working on in Cygwin, which resulted in
> a segfault in the Cygwin dll. It did not work out well though, the
> process exited with code 0. Attempting to debug with gdb gave
> [Thread 25728.0x6e60 exited with code 3221225477]
> [Thread 25728.0x33c0 exited with code 3221225477]
> [Thread 25728.0x6b44 exited with code 3221225477]
> [Thread 25728.0x5508 exited with code 3221225477]
>> Program terminated with signal SIGTRAP, Trace/breakpoint trap.
> The program no longer exists.
>>> The fact that it said SIGTRAP led me to think about the recent single step
> change.

Perhaps the singlestep code shouldn't run when under debugger control?
Corinna