From: Daniel Jacobowitz <drow@false.org>
To: Pobereznicenco Stefan <pobere@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: shared library debugging issue - please help
Date: Fri, 15 Jun 2007 12:34:00 -0000 [thread overview]
Message-ID: <20070615123417.GA3110@caradoc.them.org> (raw)
In-Reply-To: <1b19bbe60706150203m33e1cf5awc975f39fa6b54342@mail.gmail.com>
On Fri, Jun 15, 2007 at 12:03:41PM +0300, Pobereznicenco Stefan wrote:
>
> Breakpoint 1, 0xAADDRESS in LoginSM::Next () at
> /usr/lib/gcc/i386-redhat-linux/4.1.1/../../../../include/c++/4.1.1/new:93
>
> LoginSM::Next() is the function inside it I set the breakpoint, ...
> but why gdb tells me about 'new' file? I didn't set a breakpoint in
> the header file of operator 'new' ...
>
> Because of this, I cannot step into my shared library ... :(
Just single step a bit from there, or compile without optimization.
GDB does not support inlined functions yet; a call to new has been
inlined into your code.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-15 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 9:04 Pobereznicenco Stefan
2007-06-15 9:37 ` Fwd: " Pobereznicenco Stefan
2007-06-15 12:34 ` Daniel Jacobowitz [this message]
2007-06-15 14:56 ` Pobereznicenco Stefan
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=20070615123417.GA3110@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pobere@gmail.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