From: Rick Moseley <rmoseley@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk@sourceware.org
Subject: Re: Quick pc hack for exe loading
Date: Fri, 23 Nov 2007 17:14:00 -0000 [thread overview]
Message-ID: <47470A62.3070906@redhat.com> (raw)
In-Reply-To: <1195817730.2981.21.camel@dijkstra.wildebeest.org>
Hi Mark,
Cool. That ought to be fine.
Rick
Mark Wielaard wrote:
> Hi Rick,
>
> I wanted to test some libunwind lookup changes I made locally and the
> exe target is nice for that since it is so simple. The attached patch
> sets up the PC value and makes it possible to see where the exe would
> start:
>
> (fhpd) load /bin/bash
> Loaded executable file: /bin/bash
> (fhpd) where
> [0.0]
> DebugInfoStackFactory.printStackTrace() numberOfFrames 0
> #0 0x0000000000419150 in _start () from /bin/bash
>
> It still cannot actually do the other way around though:
>
> (fhpd) print _start
> [0.0]
> Error: Object _start was not found
>
> Haven't looked into why that was since I was only interested in the
> stack thing.
>
> 2007-11-23 Mark Wielaard <mwielaard@redhat.com>
>
> * LinuxExeTask.java (bankBuffers): New final field.
> (LinuxExeTask): Setup bankBuffers and explicitly set pc.
> (sendrecRegisterBanks): Use cached bankBuffers.
>
> It is a bit of a hack (as the comment explains), but it seems to work
> great and all tests still pass with this applied. Feel free to rip it
> out and completely replace with a real, less hacky, solution though.
>
> Cheers,
>
> Mark
>
next prev parent reply other threads:[~2007-11-23 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 11:35 Mark Wielaard
2007-11-23 17:14 ` Rick Moseley [this message]
2007-11-23 17:30 ` Andrew Cagney
2007-11-26 10:40 ` Mark Wielaard
2007-11-26 16:52 ` Andrew Cagney
2007-11-27 8:25 ` Mark Wielaard
2007-11-27 14:40 ` Andrew Cagney
2007-11-28 9:15 ` Mark Wielaard
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=47470A62.3070906@redhat.com \
--to=rmoseley@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.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).