This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: info registers output
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- Cc: palves at redhat dot com (Pedro Alves), gdb-patches at sourceware dot org (GDB Patches), tromey at redhat dot com (Tom Tromey), jan dot kratochvil at redhat dot com (Jan Kratochvil)
- Date: Wed, 01 Aug 2012 17:55:22 -0300
- Subject: Re: info registers output
- References: <201208012049.q71Kn9jQ011712@d06av02.portsmouth.uk.ibm.com>
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