From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: gdb patch to suppress empty lines, re-visited
Date: Wed, 11 Dec 2002 16:01:00 -0000 [thread overview]
Message-ID: <20021211235105.GA6325@nevyn.them.org> (raw)
In-Reply-To: <3DF7C9FF.63429C4D@redhat.com>
On Wed, Dec 11, 2002 at 03:27:59PM -0800, Michael Snyder wrote:
> Per Bothner wrote:
> >
> > This is a revision of a patch originally from 1999:
> > http://sources.redhat.com/ml/gdb-patches/1999-q2/msg00093.html
> >
> > I'm not sure if the patch in top.c does anything, since I don't
> > know when/if readline is called from command_line_input.
> >
> > OK to check in? With or without the top.c change?
> > --
> > --Per Bothner
>
> For posterity, this changes the console output when you are
> repeating a command a bunch of times by hitting return.
> It changes, eg.
> 1038 <main+8>: call 0x138818 <get_run_time>
> (gdb)
> 0xe103c <main+12>: st %i1, [ %fp + 0x48 ]
> (gdb)
> 0xe1040 <main+16>: st %o0, [ %fp + -464 ]
> (gdb)
>
> to
>
> (gdb) x/i $pc
> 0xe1038 <main+8>: call 0x138818 <get_run_time>
> 0xe103c <main+12>: st %i1, [ %fp + 0x48 ]
> 0xe1040 <main+16>: st %o0, [ %fp + -464 ]
> (gdb)
>
> Per, I think the first discussion needs to be,
> do we agree that we want this change? This changes
> visible behavior, quite broadly.
I'll put in my vote for "yes, or at least as an option".
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-11 23:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 23:01 Per Bothner
2002-12-11 15:38 ` Michael Snyder
2002-12-11 15:50 ` Per Bothner
2002-12-11 16:01 ` Daniel Jacobowitz [this message]
2002-12-13 12:22 ` Per Bothner
2002-12-13 12:38 ` Andrew Cagney
[not found] ` <ac131313@redhat.com>
2002-12-13 12:44 ` Kevin Buettner
2002-12-13 13:16 ` Daniel Jacobowitz
2002-12-13 13:49 ` Per Bothner
2002-12-13 12:53 ` David Carlton
2002-12-13 13:36 ` Per Bothner
2002-12-11 22:17 Michael Elizabeth Chastain
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=20021211235105.GA6325@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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