From: Nurdin <npremji@redhat.com>
To: Nurdin <npremji@redhat.com>
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: Dwfl callbacks to use frysk to get memory.
Date: Mon, 28 May 2007 20:15:00 -0000 [thread overview]
Message-ID: <465B2EFE.40108@redhat.com> (raw)
In-Reply-To: <465AF7CF.6010302@redhat.com>
Nurdin wrote:
> All the code to get elfutils to use frysk to access memory is located
> in the latest patch applied to bugzilla 4513.
> <http://sourceware.org/bugzilla/show_bug.cgi?id=4513>
>
> I have created a method Proc.getDwfl() but I am unsure as to where
> this dwfl should actually be created. (I stuck it in proc since that
> had all the necessary data to create a Dwfl, it could easily take a
> proc as a parameter and be located anywhere in the core.)
>
> Any suggestions? Should getDwfl() stay in Proc or be moved elsewhere?
As discussed on irc, it was decided the best place for this would be in
a factory, hence frysk.debuginfo.DwflFactory was created and committed.
The Dwfl objects created by this factory use frysk to read the process's
memory.
prev parent reply other threads:[~2007-05-28 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 18:49 Nurdin
2007-05-28 20:15 ` Nurdin [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=465B2EFE.40108@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).