From: Tom Tromey <tromey@redhat.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
Hui Zhu <teawater@gmail.com>
Subject: Re: [RFA] Expand "info record"
Date: Mon, 12 Oct 2009 18:10:00 -0000 [thread overview]
Message-ID: <m3pr8sv5y3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4AD36319.7010903@vmware.com> (Michael Snyder's message of "Mon, 12 Oct 2009 10:10:49 -0700")
>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:
Michael> Tom Tromey wrote:
>>>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:
>>
Michael> (gdb) info rec
Michael> Lowest recorded instruction number is 0.
>>
>> There is an extra space after "Lowest".
Michael> I know, I was just trying to line up the outputs.
Michael> Is this frowned upon?
The example again:
(gdb) info rec
Lowest recorded instruction number is 0.
Current instruction number is 46.
Highest recorded instruction number is 1016.
Max logged instructions is 200000
At first glance this did not seem to line up at all to me.
But now I see that the first and third lines to line up.
I think that is too subtle, but I suppose I don't really care that much
either way.
Tom
next prev parent reply other threads:[~2009-10-12 18:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 16:32 Michael Snyder
2009-10-12 17:06 ` Tom Tromey
2009-10-12 17:15 ` Michael Snyder
2009-10-12 18:10 ` Tom Tromey [this message]
2009-10-13 11:20 ` Pedro Alves
2009-10-13 6:03 ` Hui Zhu
2009-10-13 17:21 ` Michael Snyder
2009-10-13 18:01 ` Michael Snyder
2009-10-20 19:50 ` Michael Snyder
2009-10-20 20:54 ` Pedro Alves
2009-10-20 22:31 ` Michael Snyder
2009-10-21 0:22 ` Pedro Alves
2009-10-21 1:38 ` Michael Snyder
2009-10-21 3:09 ` Hui Zhu
2009-10-21 15:24 ` Michael Snyder
2009-10-22 2:30 ` Hui Zhu
2009-10-21 10:54 ` Pedro Alves
2009-10-21 15:23 ` Michael Snyder
2009-10-22 13:08 ` 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=m3pr8sv5y3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=teawater@gmail.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