From: Elmar Stellnberger <estellnb@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: extract debuginfo for Xorg backtraces
Date: Tue, 22 Feb 2011 16:46:00 -0000 [thread overview]
Message-ID: <AANLkTinVZuMHtvWtTMSexg7KruMHt1zsoy1D6aU=aPvi@mail.gmail.com> (raw)
In-Reply-To: <4D63D825.5080704@redhat.com>
Well, I have already resolved the problem by either just taking the
offsets for the so-s or if available by using /proc/pid/maps to
calculate them (works better).
Now the next riddle is on how to obtain the load base for a kernel
module in order to decode crashes related to kernel modules (lsmod
does not seem to be useful since it only shows the size but not the
load base).
Why is it no more possible to save the kernel`s call interface per
dd from /proc/self/mem into a file? - dd if=/proc/self/mem
of=/dld/linux-gate.so.1 skip=$((0xffffe000)) count=1 bs=4096
How does ldd obtain the kernel address 0xffffe000 of the call gate
window - it apparently does not appear in /proc/self/maps (just the
window where it shows up.). Can I open this with libbfd?
2011/2/22, Nick Clifton <nickc@redhat.com>:
> Hi Elmar,
>
>> It works well for everything in /usr/bin/Xorg. However as the
>> backtrace meets a shared library (libc.so, radeon_drv.so,
>> evdev_drv.so) the symtab does not contain any section that would
>> include the given addresses/+offsets.
>
> How about the dynamic symbol table ?
>
> I suggest that you have a look at the GDB code base to see how symbols
> in shared libraries are handled there.
>
> Cheers
> Nick
>
>
prev parent reply other threads:[~2011-02-22 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 11:46 Elmar Stellnberger
2011-02-22 15:36 ` Nick Clifton
2011-02-22 16:46 ` Elmar Stellnberger [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='AANLkTinVZuMHtvWtTMSexg7KruMHt1zsoy1D6aU=aPvi@mail.gmail.com' \
--to=estellnb@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).