Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Pobereznicenco Stefan" <pobere@gmail.com>
To: gdb@sourceware.org
Subject: Fwd: shared library debugging issue - please help
Date: Fri, 15 Jun 2007 09:37:00 -0000	[thread overview]
Message-ID: <1b19bbe60706150237j5fa657ebkc39880c27947a3e5@mail.gmail.com> (raw)
In-Reply-To: <1b19bbe60706150203m33e1cf5awc975f39fa6b54342@mail.gmail.com>

---------- Forwarded message ----------
From: Pobereznicenco Stefan <pobere@gmail.com>
Date: Jun 15, 2007 12:03 PM
Subject: shared library debugging issue - please help
To: gdb@sourceware.org


Hey,

I'm trying to debug a shared library.
I set a breakpoint like this:

(gdb) break LoginSM.cpp:153
Breakpoint 7 at 0x2cf652f: file LoginSM.cpp, line 153.

(I see that the breakpoint was set correctly!!!!!)

This file (LoginSM.cpp) is part of the shared library.

But, when the breakpoint is hit, gdb displays this:

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 ... :(

Well, if I set a breakpoint in another file, the result is the same:
the debugger stops at line 93 from 'new' file ....

Could anyone help me?

Thanks,
Stefan




well, I want to add something. If I set a breakpoint to a function, like this:
(gdb) break libmain.cpp:functionNameFromSharedLibrary
Breakpoint 7 at 0x4772c8: file
/usr/lib/gcc/i386-redhat-linux/4.1.1/../../../../include/c++/4.1.1/new,
line 93.

the breakpoint is set in "new" file !!!!!!


  reply	other threads:[~2007-06-15  9:37 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 ` Pobereznicenco Stefan [this message]
2007-06-15 12:34 ` Daniel Jacobowitz
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=1b19bbe60706150237j5fa657ebkc39880c27947a3e5@mail.gmail.com \
    --to=pobere@gmail.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