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: i386 gdbserver for windows: break problem

From: Eli Zaretskii <eliz at gnu dot org>
To: Michael Snyder <Michael dot Snyder at palmsource dot com>
Cc: lerele at champenstudios dot com, khaledjmal at yahoo dot fr, gdb at sourceware dot org
Date: Thu, 22 Feb 2007 06:09:20 +0200
Subject: Re: i386 gdbserver for windows: break problem
References: <20070221170543.14860.qmail@web26306.mail.ukl.yahoo.com> <45DC8C8C.6040007@champenstudios.com> <1172088151.9824.9.camel@localhost.localdomain>
Reply-to: Eli Zaretskii <eliz at gnu dot org>

> From: Michael Snyder <Michael.Snyder@palmsource.com>
> Cc: Khaled Jmal <khaledjmal@yahoo.fr>, gdb@sourceware.org
> Date: Wed, 21 Feb 2007 12:02:31 -0800
> 
> Control-c has always been problematic for gdb on windows.
> Windows doesn't treat control-c at all like other os's do.

Actually, Ctrl-C handling on Windows is very similar to Posix.  The
only major problem that I'm aware of is that the Ctrl-C handler runs
in a separate thread, so a single-threaded program suddenly becomes
multi-threaded, and in particular one can have race condition between
the main thread and the signal thread.

References:
- i386 gdbserver for windows: break problem
  - From: Khaled Jmal
- Re: i386 gdbserver for windows: break problem
  - From: Lerele
- Re: i386 gdbserver for windows: break problem
  - From: Michael Snyder

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