This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/683: What should ``info registers $pc'' do?
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 3 Sep 2002 20:51:57 -0000
- Subject: gdb/683: What should ``info registers $pc'' do?
- Reply-to: ac131313 at redhat dot com
>Number: 683
>Category: gdb
>Synopsis: What should ``info registers $pc'' do?
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Tue Sep 03 13:58:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: 2002-09-03
>Organization:
>Environment:
Any with $pc, $fp or $sp implemented using builtin registers.
(eg i386)
>Description:
Given:
info registers $pc
info registers fp
et.al., who should print the value.
For platforms that don't have a $pc, $fp or $sp, the builtin-code picks up the problem and converts them into variables. That way:
print $pc
works.
What should happen, though, with the above:
- refuse to print the value -- the register doesn't exist
- print the value before it gets to the target code
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="inpri"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="inpri"