Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Patrick Zou <patrick_zou@hotmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB  caused segmentation fault when stepping into C++ code in  shared library
Date: Tue, 23 Jan 2007 17:32:00 -0000	[thread overview]
Message-ID: <20070123173244.GA19197@nevyn.them.org> (raw)
In-Reply-To: <BAY124-W24A4EF294685B3C9CB64C286AD0@phx.gbl>

On Tue, Jan 23, 2007 at 05:23:08PM +0000, Patrick Zou wrote:
> 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 ?

Sorry, there is not enough information here to help you.  A testcase
would be nice; failing that, we will need at least a full transcript
of the session.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-01-23 17:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 17:23 Patrick Zou
2007-01-23 17:32 ` Daniel Jacobowitz [this message]

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=20070123173244.GA19197@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=patrick_zou@hotmail.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