This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
symtab/1294: 'info address' is not informative enough with dwarf2 location expressions
- From: ezannoni at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 23 Jul 2003 02:57:57 -0000
- Subject: symtab/1294: 'info address' is not informative enough with dwarf2 location expressions
- Reply-to: ezannoni at redhat dot com
>Number: 1294
>Category: symtab
>Synopsis: 'info address' is not informative enough with dwarf2 location expressions
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Wed Jul 23 02:58:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: ezannoni@redhat.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
If you do info address on a dwarf2 variable that is described by a location expression, (LOC_COMPUTED class, internally to gdb), you get only some vague description of the var's location. When using the old mechanism, gdb was able to tell you much more about the actual location of the variable.
See thread:
http://sources.redhat.com/ml/gdb/2003-07/msg00242.html
(gdb) info address a_thread_local
Symbol "a_thread_local" is a variable with complex or multiple locations (DWARF2).
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: