public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Nurdin Premji <npremji@redhat.com>
To: Frysk List <frysk@sourceware.org>
Subject: Need help with StackAccessors needs to implement findProcInfo and  putProcInfo
Date: Thu, 01 Mar 2007 21:17:00 -0000	[thread overview]
Message-ID: <45E742CD.8000705@redhat.com> (raw)

On the npremji-libunwind-20070228-branch

I've copied over the logic for the accessReg and accessMem accessor 
methods into StackAccessors. I have some work on the getProcName method 
using dwfl_addrname.

I now need to create logic for findProcInfo and putProcInfo methods.

I will not be able to use any of the libunwind UPT ptrace accessor 
methods as the PtraceAccessors class uses a proxy address space so it 
can call other accessor methods. The problem with this is that it seems 
as though findProcInfo calls accessMem, which won't work because it 
isn't being called in the thread that did the ptrace attach.

In short I need to implement findProcInfo and putProcInfo without 
relying on the UPT methods of the same name and I'm not sure what is 
involved in this.

             reply	other threads:[~2007-03-01 21:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 21:17 Nurdin Premji [this message]
2007-03-01 21:39 ` Roland McGrath

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=45E742CD.8000705@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).