From: Joel Brobecker <brobecker@adacore.com>
To: John Cortell <rat042@freescale.com>
Cc: gdb@sourceware.org
Subject: Re: sending CTRL-C to Cygwin gdb 6.8 has no effect
Date: Fri, 23 Apr 2010 19:44:00 -0000 [thread overview]
Message-ID: <20100423194404.GP13204@adacore.com> (raw)
In-Reply-To: <201004231941.o3NJfbWR021914@az33smr01.freescale.net>
> In CDT, we've had to resort to sending a CTRL-C to the inferior
> process of a Cygwin gdb session because gdb itself doesn't react to
> the CTRL-C. Is this a known issue? Is it addressed in HEAD?
This should have been fixed in recent versions of GDB. I don't remember
which version first started having the fix, but it's a safe bet that 7.1
will.
> Naturally, that approach isn't an option when debugging a remote
> program.
But when you are doing remote debugging, the transport protocol used
between GDB and the target should provide a way to send that interrupt.
For instance, when using the remote protocol:
http://www.sourceware.org/gdb/current/onlinedocs/gdb/Interrupts.html#Interrupts
--
Joel
next prev parent reply other threads:[~2010-04-23 19:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 19:33 John Cortell
2010-04-23 19:44 ` Joel Brobecker [this message]
2010-04-23 19:57 ` John Cortell
2010-04-23 20:11 ` Joel Brobecker
2010-04-23 20:27 ` John Cortell
2010-04-24 1:10 ` Pedro Alves
2010-04-24 1:58 ` John Cortell
2010-04-24 2:13 ` Pedro Alves
2010-04-24 22:30 ` John Cortell
2010-04-24 23:56 ` Dave Korn
2010-04-25 14:10 ` John Cortell
2010-04-25 21:25 ` Pedro Alves
2010-04-26 6:22 ` Christopher Faylor
2010-04-26 11:38 ` Pierre Muller
2010-04-26 14:30 ` Christopher Faylor
[not found] ` <201004261330.o3QDUfph028936@az33smr01.freescale.net>
2010-04-26 13:37 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100423194404.GP13204@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=rat042@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox