This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gdb-6.6 mingw port hangs after Ctrl-C

From: Eli Zaretskii <eliz at gnu dot org>
To: Daniel Jacobowitz <drow at false dot org>
Cc: Roland dot Puntaier at br-automation dot com, gdb at sourceware dot org
Date: Mon, 20 Aug 2007 22:16:12 +0300
Subject: Re: gdb-6.6 mingw port hangs after Ctrl-C
References: <OF8E457D60.CC9CEA8E-ONC125733D.005323EA-C125733D.0056FB5E@br-automation.com> <20070820162439.GA30242@caradoc.them.org>
Reply-to: Eli Zaretskii <eliz at gnu dot org>

> Date: Mon, 20 Aug 2007 12:24:39 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb@sourceware.org
> 
> Control-C handling on Windows is completely different from on
> POSIX operating systems, because the handler runs in a new thread
> instead of interrupting the main thread of execution.  This means
> that GDB's signal handling, which relies on longjmp, does not work.

The way to fix this is to make the signal handler stop the main thread
as the first thing it does.  Then you have a Posix-compliant program
again.  I did something similar for the MinGW port of GNU Make.

Follow-Ups:
- Re: gdb-6.6 mingw port hangs after Ctrl-C
  - From: Daniel Jacobowitz

References:
- gdb-6.6 mingw port hangs after Ctrl-C
  - From: Roland Puntaier
- Re: gdb-6.6 mingw port hangs after Ctrl-C
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]