DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 562AalFC3770826
Date: Wed, 2 Jul 2025 12:35:45 +0200
To: cygwin@cygwin.com
Subject: Re: issues debugging crash in cygwin dll with gdb
Message-ID: <aGULgR1RsU2g57Go@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <7a97c9a4-43bd-37ef-bde2-5f8e5abd29b4@jdrake.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <7a97c9a4-43bd-37ef-bde2-5f8e5abd29b4@jdrake.com>
Precedence: list
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

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

-- 
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