From: Daniel Jacobowitz <drow@mvista.com>
To: Jack J <get_info101@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: debugging dynamic link/load code on Linux
Date: Wed, 15 Oct 2003 20:14:00 -0000 [thread overview]
Message-ID: <20031015201401.GA2425@nevyn.them.org> (raw)
In-Reply-To: <20031015201057.77923.qmail@web20510.mail.yahoo.com>
On Wed, Oct 15, 2003 at 01:10:57PM -0700, Jack J wrote:
> Hi,
>
> I am new to gdb mailing list.
> I have a question and if this list is not appropriate,
> please apologize. I am hoping someone can shed some
> light with helpful tips and pointers.
>
> question: How do I set a breakpoint in a module/code
> which is dynamically linked/loaded in Linux ?
>
> I tried setting a breaking point (in gdb) after
> dlsym() but, gdb still complains of function not
> found.
> I did have it compiled with "-g" gcc option.
>
> -- gdb output--
>
> (gdb) b test_routine
> Function "test_routine" not defined.
> (gdb) l test_routine
> Function "test_routine" not defined.
Once the library has been loaded you should be able to. Can you build
a small testcase, and a complete session transcript that show the
problem?
Does "info shared" show the module?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-10-15 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 20:11 Jack J
2003-10-15 20:14 ` 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=20031015201401.GA2425@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=get_info101@yahoo.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