From: Nurdin Premji <npremji@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: Re: 32-64 problem with lib.unwind.ProcInfo
Date: Mon, 18 Jun 2007 22:26:00 -0000 [thread overview]
Message-ID: <4676FAE0.7080109@redhat.com> (raw)
In-Reply-To: <4672DC43.1020300@redhat.com>
Nurdin Premji wrote:
> ProcInfo has a challenge dealing with non-native architectures with
> unw_word_t being assumed to be the native architecture case rather
> than the remote case.
>
> I'll look at this Monday.
Fixed, ProcInfo now has a reference to an Unwind object and the Unwind
defines the methods to access the ProcInfo's fields. Thus the ProcInfo
field accessors are defined in one of UnwindX86, UnwindX8664,
UnwindPPC64 and so forth to follow.
prev parent reply other threads:[~2007-06-18 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 19:27 Nurdin Premji
2007-06-18 22:26 ` Nurdin Premji [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=4676FAE0.7080109@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).