From: Michael Snyder <msnyder@vmware.com>
To: gdb@sourceware.org
Subject: [bug] problem printing local vars in shared lib function
Date: Mon, 27 Oct 2008 23:10:00 -0000 [thread overview]
Message-ID: <490648CE.4090709@vmware.com> (raw)
Does this sound familiar to anybody? X86_64...
I have a local shared library function, built with -g,
gdb has its symbols and can list it, step into it, step
within it etc.
I can print the values of the function parameters, but
not the values of local (automatic) variables. These
are not statics but autos on the stack.
GDB complains that the memory is inaccessible when
I use "print", but if I use "examine" ('x'), it works
fine and displays the value.
Doesn't seem to matter what the type of the variable is.
Stack variables in the main executable program (ie. not
in the shared library) work fine.
I've even tried this with -gstabs as opposed to dwarf.
Same symptom.
Executable: GNU gdb 6.8-debian
OS: Ubuntu Hardy (8.0.4) x86_64, kernel 2.6.24-19-generic
next reply other threads:[~2008-10-27 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 23:10 Michael Snyder [this message]
2008-10-28 8:08 ` André Pönitz
2008-10-28 18:06 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=490648CE.4090709@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox