From: Nurdin Premji <npremji@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: frysk/rt/StackAccessors.java#getElfImage() suggestions?
Date: Fri, 27 Apr 2007 14:35:00 -0000 [thread overview]
Message-ID: <463116DC.7000903@redhat.com> (raw)
The method getElfImage() inside of frysk/rt/StackAccessors.java
currently depends on a running process. It is used by libunwind to map
an elfImage (or vdso segment) into local memory. It works by finding
the elf image file name and mmapping it into memory, also keeping track
of the offset into the file that was mapped, and the lowAddress of that
segment (as displayed in proc/$$/maps).
The question is how to refactor this to account for core processes.
One way is by using a Proc.getElfImageInfo method that could return the
name, lowAddress, and offset fields to the getElfImage and it would just
map that file. The problem comes with the vdso section, mapping this
section would be different between core and running processes. There is
a method: lib.unwind.Unwind.createElfImageFromVDSO (might be better to
call it ...FromRunningProcessVDSO) which will create an elfImage from a
running processes vdso so perhaps a similar method for core process VDSO
could be created.
Any suggestions?
reply other threads:[~2007-04-26 21:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=463116DC.7000903@redhat.com \
--to=npremji@redhat.com \
--cc=frysk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).