From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: sunil <sunil.vvn@gmail.com>
Cc: gdb ml <gdb@sourceware.org>
Subject: Re: Regarding shared library and GDB
Date: Wed, 03 Oct 2007 20:37:00 -0000 [thread overview]
Message-ID: <1191443859.5203.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1190876904.724372.33360@r29g2000hsg.googlegroups.com>
Hi,
Changing the discussion to this mailing list since it seems more
appropriate.
On Thu, 2007-09-27 at 00:08 -0700, sunil wrote:
> Am interested to debug one shared library using GDB.This shared
> libarry is used by a binary (for which i doesn't have the code).I am
> aware about at what point of time the library will be called.
> Can i debug that library iusing GDB.If yes please let me know the
> steps how to proceed further.
If the library has debug information, you should be able to set a
pending breakpoint on a function in the library. It will be resolved by
GDB when it gets loaded by the binary. You don't need source code or
debug information for the main program if all you are interested in is
the library.
--
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center
parent reply other threads:[~2007-10-03 20:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1190876904.724372.33360@r29g2000hsg.googlegroups.com>]
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=1191443859.5203.6.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb@sourceware.org \
--cc=sunil.vvn@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