Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Tom Tromey <tom@tromey.com>, "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Philippe Waroquiers via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PUSHED/OBVIOUS] Remove gdb-gdb.gdb breakpoint on disappeared function info_command.
Date: Sun, 03 May 2020 20:33:52 +0200	[thread overview]
Message-ID: <6788389efac939abdd991b558528db606b25c2a6.camel@skynet.be> (raw)
In-Reply-To: <87ftch0wg8.fsf@tromey.com>

On Sun, 2020-05-03 at 11:17 -0600, Tom Tromey wrote:
> > > > > > "Maciej" == Maciej W Rozycki <macro@linux-mips.org> writes:
> 
> Maciej>  Its use was quite obvious to anyone who actually debugged GDB from time 
> Maciej> to time:
> 
> What was the point of the "return"?
As I understand, the idea of "info"/"i" was just to have the top-gdb
regaining control.  The return avoids the (long) output of "info"

> 
> Maciej>  So what's the current mechanism to do that?  I do hope to have it the 
> Maciej> next time I poke at GDB.
> 
> You can break in "do_prefix_cmd".
But that will break on all commands showing a list, not only on "info".

Philippe




  reply	other threads:[~2020-05-03 18:33 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
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 [this message]
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=6788389efac939abdd991b558528db606b25c2a6.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=tom@tromey.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