linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Karim Yaghmour <karym@opersys.com>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: Anton Blanchard <anton@linuxcare.com.au>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: ltrace for ppc
Date: Fri, 16 Feb 2001 15:58:57 -0500	[thread overview]
Message-ID: <3A8D8F81.7BB25F04@opersys.com> (raw)
In-Reply-To: 20010215124800.A22625@drow.them.org


If you're interested in ltrace, you may want to take a look at the
Linux trace toolkit (http://www.opersys.com/LTT). It runs fine
on PPC too.

Best regards,

Karim

Daniel Jacobowitz wrote:
>
> 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      |
> \--------------------------------/  \--------------------------------/
>

--
===================================================
                 Karim Yaghmour
               karym@opersys.com
          Operating System Consultant
 (Linux kernel, real-time and distributed systems)
===================================================

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-02-16 20:58 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
2001-02-16 20:58   ` Karim Yaghmour [this message]
  -- 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=3A8D8F81.7BB25F04@opersys.com \
    --to=karym@opersys.com \
    --cc=anton@linuxcare.com.au \
    --cc=dmj+@andrew.cmu.edu \
    --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 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 NNTP newsgroup(s).