This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/834: Dwarf2 reader cannot find local variables
- From: jakub at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Cc: jimb at redhat dot com, kevinb at redhat dot com
- Date: 16 Nov 2002 20:42:03 -0000
- Subject: gdb/834: Dwarf2 reader cannot find local variables
- Reply-to: jakub at redhat dot com
>Number: 834
>Category: gdb
>Synopsis: Dwarf2 reader cannot find local variables
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Nov 16 12:48:02 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: jakub@redhat.com
>Release: 5.2.1-2
>Organization:
>Environment:
RHL 8.0
>Description:
I'm experiencing lots of problems when using dwarf2,
mostly variables gdb knows nothing about, while with stabs it works just
fine.
One testcase is in
ftp://ultra.linux.cz/private/gdb-testcase/binutils-gdb-problem.tar.bz2
>How-To-Repeat:
tar xjf binutils-gdb-problem.tar.bz2
cd binutils/obj/ld
gdb ./ld-new
There is .gdbinit which will show that lots of local variables are
not known to gdb at all, like:
p r_type
No symbol "r_type" in current context.
p r_symndx
No symbol "r_symndx" in current context.
p unresolved_reloc
No symbol "unresolved_reloc" in current context.
At least quick skimming of readelf -wi output shows the variables are
present in .debug_info (e.g. r_type should be in %esi register).
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: