From: Pupeno <pupeno@pupeno.com>
To: gdb@sourceware.org
Subject: debugging dynamically loadable code
Date: Mon, 03 Apr 2006 16:09:00 -0000 [thread overview]
Message-ID: <200604031809.35814.pupeno@pupeno.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
Hello, hope this is not off-topic,
I need to debug some code that is located in a dynamic library, a .so file.
This file is loaded by a program at run-time (with dlopen I supouse). So I
load this program into gdb (using ddd) and my problem is that I can't open
the yet-unloaded sources and/or set a break point on them.
If I run the program to let it load the .so file it'll be too late because I
need to debug the module initialization code.
I know I should put a breakpoint between the loading and the running of the
module, but I can't find it. The module is loaded thru a custom script this
application interprets, so, it's hard to dig that code.
Any ideas how can I do my debugging ?
Thank you.
--
Pupeno <pupeno@pupeno.com> (http://pupeno.com)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-04-03 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 16:09 Pupeno [this message]
2006-04-03 16:35 ` Daniel Jacobowitz
2006-04-03 21:23 ` Pupeno
2006-04-03 21:27 ` Daniel Jacobowitz
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=200604031809.35814.pupeno@pupeno.com \
--to=pupeno@pupeno.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