From: Patrick Zou <patrick_zou@hotmail.com>
To: <gdb@sources.redhat.com>
Subject: GDB caused segmentation fault when stepping into C++ code in shared library
Date: Tue, 23 Jan 2007 17:23:00 -0000 [thread overview]
Message-ID: <BAY124-W24A4EF294685B3C9CB64C286AD0@phx.gbl> (raw)
Hi,
I have some C++ code in shared library, I used set solib-absoluate-prefix and loaded in those libs at the point where I need to exam the source codes. When I stepped into those codes, (the first one is new an object), GDB complained segmentation fault. The code runs OK without gdb though.
Stepping into C++ in current exe is OK.
I even set a breakpoint in the shared library, but not hit either. Wondering the lib is not mapped correctly. Some of you must have made this work, I believe. Any idea? is the way I compile my codes or some GDB configuration ?
I am using gdb6.3 to remotely debug an embedded system on Arm.
thanks
patrick
_________________________________________________________________
Fixing up the home? Live Search can help.
http://imagine-windowslive.com/search/kits/default.aspx?kit=improve&locale=en-US&source=wlmemailtaglinenov06
next reply other threads:[~2007-01-23 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 17:23 Patrick Zou [this message]
2007-01-23 17:32 ` Daniel Jacobowitz
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=BAY124-W24A4EF294685B3C9CB64C286AD0@phx.gbl \
--to=patrick_zou@hotmail.com \
--cc=gdb@sources.redhat.com \
/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