From: Daniel Jacobowitz <drow@false.org>
To: Thomas Ackermann <tja@anykey.de>
Cc: gdb@sourceware.org
Subject: Re: Help with debugging LD_PRELOADed shared C libraries
Date: Thu, 13 Jul 2006 17:40:00 -0000 [thread overview]
Message-ID: <20060713174040.GA30455@nevyn.them.org> (raw)
In-Reply-To: <4570013.1152812286324.OPEN-XCHANGE.WebMail.wwwrun@eu.main.anykey>
On Thu, Jul 13, 2006 at 07:38:06PM +0200, Thomas Ackermann wrote:
> It does not:
>
> Cannot access memory at address 0x4001738c
> #0 0x400cc9b8 in ?? ()
> (gdb) info shared
> Cannot access memory at address 0x4001738c
> (gdb)
>
>
> Are you sure that this is true for a shared library that is loaded vias
> LD_PRELOAD? I mean, it is supposed to exchange functions from the binary
> - to which i have no source.
Absolutely sure.
It looks to me as if your kernel did not write out the _DYNAMIC segment
for some reason. What does "readelf -l core" say? How about "readelf
-l application"?
> > Are you sure that core dumps work on this system?
>
> How to easy test this?
> I seem to remember using gdb on this system in earlier times already.
cat&
killall -ABRT <pid of cat>
Then try loading that core dump.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-13 17:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 16:47 Thomas Ackermann
2006-07-13 17:05 ` Daniel Jacobowitz
2006-07-13 17:38 ` Thomas Ackermann
2006-07-13 17:40 ` Daniel Jacobowitz [this message]
2006-07-13 18:55 ` Thomas Ackermann
2006-07-13 19:10 ` Daniel Jacobowitz
2006-07-13 22:14 ` Thomas Ackermann
2006-07-13 22:29 ` Daniel Jacobowitz
2006-07-14 1:22 ` Russell Shaw
2006-07-14 14:33 ` Thomas Ackermann
2006-07-14 16:31 ` 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=20060713174040.GA30455@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=tja@anykey.de \
/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