All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: linux-parisc@vger.kernel.org, debian-hppa@lists.debian.org
Subject: Re: Fixed strace [ was Re: ls -l is broken ]
Date: Sat, 09 May 2009 10:39:59 +0800	[thread overview]
Message-ID: <4A04ECFF.7090308@tausq.org> (raw)
In-Reply-To: <20090507210853.GD30675@bombadil.infradead.org>


> Sadly, I can't seem to reproduce this right now, because strace is dying
> with the ptrace issue JDA brought up earlier. I'll poke at it more
> tonight, but I want to get caught up on the merging first.
>
> cheers, Kyle
>   
Kyle suggested I mention atrace to the strace developers. Maybe others 
here are interested:

http://sourceforge.net/mailarchive/forum.php?thread_name=4A04EB4A.5030204%40tausq.org&forum_name=strace-devel

For all I know, atrace is also horribly broken, but at least it seems to 
be able to trace "ls -l"   :-)

randolph

  reply	other threads:[~2009-05-09  2:39 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06 22:28 ls -l is broken John David Anglin
2008-04-06 22:42 ` Matthew Wilcox
2008-04-06 23:09   ` John David Anglin
2008-04-15  5:16     ` Kyle McMartin
2008-04-16 14:27       ` Kyle McMartin
2008-04-16 17:15         ` John David Anglin
2008-04-16 17:21           ` Kyle McMartin
2008-04-17  7:53     ` Fixed strace [ was Re: ls -l is broken ] Kyle McMartin
2008-08-04 19:39       ` John David Anglin
2008-08-07 21:08         ` Kyle McMartin
2008-08-07 21:14           ` John David Anglin
2009-05-02 22:34       ` John David Anglin
2009-05-02 23:43         ` Kyle McMartin
2009-05-05  3:46           ` Mike Frysinger
2009-05-05 15:37             ` Kyle McMartin
2009-05-05 16:14               ` Kyle McMartin
2009-05-05 19:47               ` Mike Frysinger
2009-05-05 17:05             ` Kyle McMartin
2009-05-05 17:22         ` Kyle McMartin
2009-05-05 18:17           ` John David Anglin
2009-05-05 18:40             ` Kyle McMartin
2009-05-05 19:09               ` John David Anglin
2009-05-05 19:18                 ` Kyle McMartin
2009-05-05 19:46                   ` John David Anglin
2009-05-06 16:04                     ` Kyle McMartin
2009-05-06 16:19                       ` John David Anglin
2009-05-06 16:25                         ` Kyle McMartin
2009-05-06 17:39                           ` John David Anglin
2009-05-07 16:52                             ` Kyle McMartin
2009-05-07 17:41                               ` John David Anglin
2009-05-07 18:37                                 ` Kyle McMartin
2009-05-07 18:41                                   ` John David Anglin
2009-05-07 21:06                                     ` James Bottomley
2009-05-07 21:08                                       ` Kyle McMartin
2009-05-09  2:39                                         ` Randolph Chung [this message]
2009-05-09 17:18                               ` John David Anglin
2009-05-09 21:11                                 ` Carlos O'Donell
2009-05-09 21:40                                   ` John David Anglin
2009-05-14  4:50                       ` Grant Grundler
2009-05-14 13:31                         ` John David Anglin
2008-04-06 23:37   ` ls -l is broken John David Anglin
2008-04-11 17:41 ` Kyle McMartin
2008-04-11 18:00   ` Kyle McMartin

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=4A04ECFF.7090308@tausq.org \
    --to=randolph@tausq.org \
    --cc=debian-hppa@lists.debian.org \
    --cc=linux-parisc@vger.kernel.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.