From: Chuck Ebbert <76306.1226@compuserve.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Problem: strace -ff fails on 2.4.21-rc1
Date: Wed, 7 May 2003 10:08:37 -0400 [thread overview]
Message-ID: <200305071011_MC3-1-37CE-FD16@compuserve.com> (raw)
Is this a bug or a feature? Machine only has 1 CPU, if that makes
any difference:
# strace -q -o minicom.trc -tt -ff minicom
upeek: ptrace(PTRACE_PEEKUSER, ... ): Operation not permitted
detach: ptrace(PTRACE_CONT, ...): Operation not permitted
Device /dev/ttyS1 lock failed: No child processes.
# uname -a
Linux d2 2.4.21-rc1 #1 SMP Wed May 7 06:05:31 EDT 2003 i686 unknown
(Ignore that minicom error message about the lock failing -- that's
a separate problem...)
next reply other threads:[~2003-05-07 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 14:08 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 7:50 Problem: strace -ff fails on 2.4.21-rc1 Chuck Ebbert
2003-05-09 9:11 Chuck Ebbert
2003-05-09 12:15 ` Carl-Daniel Hailfinger
2003-05-11 15:37 Chuck Ebbert
2003-05-11 23:50 ` Bernhard Kaindl
2003-05-12 0:33 ` Daniel Jacobowitz
2003-05-12 1:03 Chuck Ebbert
2003-05-12 8:20 ` Russell King
2003-05-12 11:28 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=200305071011_MC3-1-37CE-FD16@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox