From: Roland McGrath <roland@redhat.com>
To: Nurdin Premji <npremji@redhat.com>
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: Need help with StackAccessors needs to implement findProcInfo and putProcInfo
Date: Thu, 01 Mar 2007 21:39:00 -0000 [thread overview]
Message-ID: <20070301213917.E5B9E180065@magilla.sf.frob.com> (raw)
In-Reply-To: Nurdin Premji's message of Thursday, 1 March 2007 16:17:01 -0500 <45E742CD.8000705@redhat.com>
As I recall, those callbacks are dismally designed. What you'll have to
figure out is how to hook back in to the DWARF-format grovelling code in
libunwind. It doesn't look good, it's all so poorly structured. I think
you'll have to cannibalize some code from the ptrace parts of libunwind,
because for no good reason it has parts of the DWARF format header parsing
there (and the different ia64 version). libdwfl will take you from a PC to
getting the libelf handles open on the ELF files containing the .eh_frame
or .debug_frame section to point libunwind at.
prev parent reply other threads:[~2007-03-01 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 21:17 Nurdin Premji
2007-03-01 21:39 ` Roland McGrath [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=20070301213917.E5B9E180065@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=frysk@sourceware.org \
--cc=npremji@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).