From: Mike Coleman <mkc@mathdogs.com>
To: Ian Stirling <root@mauve.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why can't I strace some processes?
Date: 04 Nov 2001 14:45:04 -0600 [thread overview]
Message-ID: <877kt6uuy7.fsf@mathdogs.com> (raw)
In-Reply-To: <200110121535.QAA30537@mauve.demon.co.uk>
In-Reply-To: <200110121535.QAA30537@mauve.demon.co.uk>
Ian Stirling <root@mauve.demon.co.uk> writes:
> Details: Kernel 2.4.11 strace 4.4 (neither of these seem critical.
> http://www.edonkey2000.com/files/ed2k_linux_gui_0.1alpha.tar.gz Has a binary
> of a p2p client for linux. It's closed-source, and has a number of issues.
> In attempts to find workarounds for these, I attempted to strace the
> process, and it diddn't quite work.
>
> It only ever traces syscalls made by the process that originated the
> clone call, never resultant processes, even with -f set.
> Attempring to connect and trace the resultant processes causes strace to
> exit immediately, sometimes STOPing the process that was attempted to
> be traced.
AFAIK, strace 4.4 doesn't know how to trace clone/threads. I think they're
working on adding the capability. If you're desperate, you can try
subterfugue, which can trace clone/threads, although it's alpha code and has
some other problems. (There's a debian package, or see www.subterfugue.org.)
Mike
prev parent reply other threads:[~2001-11-04 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 8:16 Why can't I strace some processes? Ian Stirling
2001-10-12 15:35 ` Ian Stirling
2001-11-04 20:45 ` Mike Coleman [this message]
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=877kt6uuy7.fsf@mathdogs.com \
--to=mkc@mathdogs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@mauve.demon.co.uk \
/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