Re: issues debugging crash in cygwin dll with gdb

2025-07-02 Thread Jon Turney via Cygwin
On 02/07/2025 00: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 32

Re: issues debugging crash in cygwin dll with gdb

2025-07-02 Thread Corinna Vinschen via Cygwin
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

issues debugging crash in cygwin dll with gdb

2025-07-01 Thread Jeremy Drake via Cygwin
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 322122