From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PUSHED/OBVIOUS] Remove gdb-gdb.gdb breakpoint on disappeared function info_command.
Date: Sat, 2 May 2020 16:57:15 -0700 [thread overview]
Message-ID: <20200502165715.506efd68@f31-4.lan> (raw)
In-Reply-To: <6dd0b78d43594ff851005a389e4a1579df546c51.camel@skynet.be>
On Sun, 03 May 2020 01:01:26 +0200
Philippe Waroquiers <philippe.waroquiers@skynet.be> wrote:
> On Sat, 2020-05-02 at 22:19 +0100, Maciej W. Rozycki wrote:
>
> > Its use was quite obvious to anyone who actually debugged GDB from time
> > to time: it was there so that you could break from the debuggee GDB into
> > the debugger GDB with the use of the `info' command (with no arguments),
> > as obviously using signals like SIGINT for that was quite problematic. I
> > used to use this feature regularly, up until the last time a couple months
> > back when I switched to non-GDB work.
> I do limited GDB debugging, but was not aware of this feature.
> I am not sure to understand the problem:
> C-c works for me to interrupt GDB, and the top GDB gets
> back the control (I typically launch top-gdb separately
> and attach to the inferior GDB).
FWIW, I also use Ctrl-C do get back to the top GDB.
I'd also like to understand the use case when this is problematic.
Kevin
next prev parent reply other threads:[~2020-05-02 23:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 14:54 Philippe Waroquiers
2020-05-02 4:02 ` Kevin Buettner
2020-05-02 21:19 ` Maciej W. Rozycki
2020-05-02 23:01 ` Philippe Waroquiers
2020-05-02 23:57 ` Kevin Buettner [this message]
2020-05-03 0:13 ` Maciej W. Rozycki
2020-05-03 0:33 ` Simon Marchi
2020-05-03 11:03 ` Pedro Alves
2020-05-03 12:45 ` Philippe Waroquiers
2020-05-03 17:17 ` Tom Tromey
2020-05-03 18:33 ` Philippe Waroquiers
2020-05-04 21:21 ` Tom Tromey
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=20200502165715.506efd68@f31-4.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
/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