From: Sergio Durigan Junior <sergiodj@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: palves@redhat.com (Pedro Alves),
gdb-patches@sourceware.org (GDB Patches),
tromey@redhat.com (Tom Tromey),
jan.kratochvil@redhat.com (Jan Kratochvil)
Subject: Re: info registers output
Date: Wed, 01 Aug 2012 20:55:00 -0000 [thread overview]
Message-ID: <m3wr1ijps5.fsf@redhat.com> (raw)
In-Reply-To: <201208012049.q71Kn9jQ011712@d06av02.portsmouth.uk.ibm.com> (Ulrich Weigand's message of "Wed, 1 Aug 2012 22:49:09 +0200 (CEST)")
On Wednesday, August 01 2012, Ulrich Weigand wrote:
> Pedro Alves wrote:
>> Ah. I wonder if that's been made on purpose. You get this on amd64:
>>
>> (gdb) info registers rip pc
>> rip 0x390f407e68 0x390f407e68 <start_thread+552>
>> pc: 0x390f407e68
>>
>> GDB knows the type of "pc", and so should be able to print "pc" like "rip".
>>
>> Would that be a good idea?
>
> Would make sense to me. (In fact, there probably ought to be a single
> routine to print a register, called by both code paths, to avoid having
> the code diverge again in the future ...)
FWIW I created sourceware.org/bugzilla/show_bug.cgi?id=14428 for this.
Thanks,
--
Sergio
next prev parent reply other threads:[~2012-08-01 20:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 21:26 [PATCH] Adjust `pc-fp.exp' for ppc64/s390x (PR 12659) Sergio Durigan Junior
2012-07-31 23:29 ` Andreas Schwab
2012-08-01 3:06 ` Sergio Durigan Junior
2012-08-01 9:22 ` Andreas Schwab
2012-08-01 8:46 ` Pedro Alves
2012-08-01 19:41 ` Ulrich Weigand
2012-08-01 19:47 ` Sergio Durigan Junior
2012-08-01 20:20 ` info registers output Pedro Alves
2012-08-01 20:49 ` Ulrich Weigand
2012-08-01 20:55 ` Sergio Durigan Junior [this message]
2012-08-27 17:41 ` Pedro Alves
2012-08-28 0:41 ` Ulrich Weigand
2012-08-28 9:07 ` Pedro Alves
2012-08-01 19:52 ` [PATCH] Adjust `pc-fp.exp' for ppc64/s390x (PR 12659) Tom Tromey
2012-08-01 20:23 ` Pedro Alves
2012-08-01 20:49 ` Sergio Durigan Junior
2012-08-01 21:44 ` Pedro Alves
2012-08-01 22:03 ` Andreas Schwab
2012-08-01 23:40 ` Sergio Durigan Junior
2012-08-02 9:06 ` Pedro Alves
2012-08-02 20:38 ` Sergio Durigan Junior
2012-08-08 11:57 ` Mark Kettenis
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=m3wr1ijps5.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=tromey@redhat.com \
--cc=uweigand@de.ibm.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