From: Daniel Jacobowitz <dan@debian.org>
To: Albert Cahalan <acahalan@gmail.com>
Cc: torvalds@osdl.org, alan@lxorguk.ukuu.org.uk, ak@suse.de,
mingo@elte.hu, arjan@infradead.org, akpm@osdl.org,
linux-kernel@vger.kernel.org, roland@redhat.com
Subject: Re: ptrace bugs and related problems
Date: Mon, 31 Jul 2006 21:37:08 -0400 [thread overview]
Message-ID: <20060801013708.GA25965@nevyn.them.org> (raw)
In-Reply-To: <787b0d920607311708y3642e41cue49cd47ccc39e77d@mail.gmail.com>
On Mon, Jul 31, 2006 at 08:08:35PM -0400, Albert Cahalan wrote:
> The execve event is unreliable anyway.
> Thus, it is necessary to use syscall tracing.
You keep saying this "unreliable" thing, and I don't think it means
what you think it means. It should always be delivered. When it
isn't, there's a bug. I don't know of any, unless you're talking about
the thread group issue you just reported.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-01 1:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 6:55 ptrace bugs and related problems Albert Cahalan
2006-07-27 7:19 ` David Miller
2006-07-27 20:31 ` Daniel Jacobowitz
2006-07-28 1:17 ` Albert Cahalan
2006-07-28 3:47 ` Daniel Jacobowitz
2006-07-28 22:28 ` Albert Cahalan
2006-07-28 22:36 ` David Miller
2006-07-31 19:00 ` Daniel Jacobowitz
2006-08-01 0:08 ` Albert Cahalan
2006-08-01 1:37 ` Daniel Jacobowitz [this message]
2006-08-01 5:22 ` Albert Cahalan
-- strict thread matches above, loose matches on Subject: below --
2006-07-28 20:07 Chuck Ebbert
2006-07-31 6:21 Chuck Ebbert
2006-08-01 0:30 ` Albert Cahalan
2006-08-01 5:52 Chuck Ebbert
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=20060801013708.GA25965@nevyn.them.org \
--to=dan@debian.org \
--cc=acahalan@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=torvalds@osdl.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