From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Anton Blanchard <anton@linuxcare.com.au>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ltrace for ppc
Date: Thu, 15 Feb 2001 12:48:01 -0500 [thread overview]
Message-ID: <20010215124800.A22625@drow.them.org> (raw)
In-Reply-To: <20010214081000.A28509@linuxcare.com>; from anton@linuxcare.com.au on Wed, Feb 14, 2001 at 08:10:00AM +1100
On Wed, Feb 14, 2001 at 08:10:00AM +1100, Anton Blanchard wrote:
>
> Hi,
>
> ltrace is a cool little program for tracing library calls. I ported it
> to ppclinux a while ago but the ltrace maintainer seems to have ignored
> my patch.
>
> For anyone interested the patch can be found at:
>
> http://linuxcare.com.au/anton/patches/ltrace_ppc_patch
>
> It should apply cleanly to the latest source (I got mine from the debian
> archive).
You did? Wow! I spent ages trying to do this...
Oh, looking at your patch I remember what happened. It's a bloody
miracle that ltrace works at all on any architecture; the PLT tricks
that the PPC plays are not at all uncommon, as I recall. I got
derailed trying to make it insert breakpoints at the proper time.
Thanks for the patch; I'll probably keep bugging the author about
this...
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-15 17:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 21:10 ltrace for ppc Anton Blanchard
2001-02-15 17:48 ` Daniel Jacobowitz [this message]
2001-02-16 20:58 ` Karim Yaghmour
-- strict thread matches above, loose matches on Subject: below --
2001-02-16 21:10 Iain Sandoe
2001-02-16 22:47 ` Tony Mantler
2001-02-17 12:18 ` Anton Blanchard
2001-02-17 21:11 ` Thomas Graichen
2001-02-16 23:29 ` Karim Yaghmour
2001-02-16 23:16 Iain Sandoe
2001-02-16 23:45 Iain Sandoe
2001-02-17 0:07 Iain Sandoe
2001-02-17 0:22 ` Karim Yaghmour
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=20010215124800.A22625@drow.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=anton@linuxcare.com.au \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.