Re: [cdt-dev] target unexpectedly stops on a SIGINT while setting breakp

[Daniel Jacobowitz <dan@xxxxxxxxxxxxxxxx>]

On Tue, Mar 02, 2010 at 05:52:39PM -0600, John Cortell wrote:
>    I'm encountering an intermittent problem setting a breakpoint while the
>    target is running on mingw/gdb 7.0. The target ends up becoming
>    unexpectedly suspended because of a SIGINT.
> 
>    The target program is in the middle of a Win32 Sleep() call when I try to
>    set the breakpoint. The next thing I expect to happen is that the
>    breakpoint is hit. Instead, the target stops in an unexpected location.
>    Interestingly enough, gdb seems to warn the debugger that this is going to
>    happen (see bold/red trace line below). Any gdb experts out there know why
>    this is happening?

Interrupting things on Windows is a mess.  The fact that for
historical reasons, CDT does this by sending an actual C-c or
DebugBreak to GDB makes it even worse.

The real solution to this problem is to not interrupt GDB.  Instead,
drive GDB in asynchronous mode.  Then send -exec-interrupt.  We've
made some big contributions to GDB over the last two years to make
this work smoothly.

I think DSF does, or can do, this.  Marc Khouzam should know for sure.

-- 
Daniel Jacobowitz
CodeSourcery