This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
symtab/1370: debug info register range / iterator?
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 5 Sep 2003 20:19:43 -0000
- Subject: symtab/1370: debug info register range / iterator?
- Reply-to: ac131313 at redhat dot com
>Number: 1370
>Category: symtab
>Synopsis: debug info register range / iterator?
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: maintenance
>Submitter-Id: net
>Arrival-Date: Fri Sep 05 20:28:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
As best I can tell, there is no well defined way to determine the maximum valid debug info register (ex dwarf2 register number rather than a core GDB regnum) or efficently iterate over those registers.
Can DWARF2_REG_TO_REGNUM et.al. be extended to specify this, or perhaphs a new method be provided. Eg: have *_REG_TO_REGNUM return the -ve of the upper bound? Wouldn't be efficient when the debug info registers have large holes (e.g., e500 registers).
Why? I need to iterate over all valid dwarf2 debug info registers to determine which were not specified by CFI.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: