From: Chuck Ebbert <76306.1226@compuserve.com>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem: strace -ff fails on 2.4.21-rc1
Date: Fri, 9 May 2003 03:50:30 -0400 [thread overview]
Message-ID: <200305090352_MC3-1-3815-126D@compuserve.com> (raw)
Ingo Oeser wrote:
>> # 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
>
> Is minicom a SUID binary, like on my machine? E.g. does
>
> ls -la $(which minicom)
>
> show
>
> -rwxr-sr-x 1 root uucp 130664 Feb 21 1998 /usr/bin/minicom
>
> ?
>
> SUID binaries cannot be ptrace()d under Linux for security reasons.
No, it's not suid. Rather than do that I changed the permissions
on /dev/ttyS1 so my normal userid could open it.
And the strace works -- until minicom forks and then the trace fails
to attach to the child. Both root and a normal userid fail with the
above messages; it works on 2.5.68.
(BTW does minicom work for you on 2.5? It fails with the "No child
processes" message on 2.5.6x here but works on 2.4 when it's not being
traced. Just the very act of running it under strace on 2.4 makes it
fail the same way it does on 2.5 here. And stracing it on 2.5.66 made
it start working again! Something very strange is going on...)
next reply other threads:[~2003-05-09 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 7:50 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 11:28 Problem: strace -ff fails on 2.4.21-rc1 Chuck Ebbert
2003-05-12 1:03 Chuck Ebbert
2003-05-12 8:20 ` Russell King
2003-05-11 15:37 Chuck Ebbert
2003-05-11 23:50 ` Bernhard Kaindl
2003-05-12 0:33 ` Daniel Jacobowitz
2003-05-09 9:11 Chuck Ebbert
2003-05-09 12:15 ` Carl-Daniel Hailfinger
2003-05-07 14:08 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=200305090352_MC3-1-3815-126D@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--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;
as well as URLs for NNTP newsgroup(s).