From: Wichert Akkerman <wichert@wiggy.net>
To: strace-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: strace 4.4 released
Date: Sun, 19 Aug 2001 15:02:48 +0200 [thread overview]
Message-ID: <20010819150248.B1021@wiggy.net> (raw)
What is strace?
---------------
strace is a system call tracer, i.e. a debugging tool which prints out a
trace of all the system calls made by a another process/program. The
program to be traced need not be recompiled for this, so you can use it
on binaries for which you don't have source.
System calls and signals are events that happen at the user/kernel
interface. A close examination of this boundary is very useful for bug
isolation, sanity checking and attempting to capture race conditions.
What has changed?
-----------------
A fair number of things have been changed since the last announced
release which was version 4.2. For a complete list of changes please see
the ChangeLog file in the source. The highlights are:
* Linux hppa, ia64 and s390 ports added
* The usual Linux syscall updates (includes 32bit uid/gid support),
* Linux ioctl handling code rewritten to be simpler as well as decode
more ioctls
* Supports IPv6 scope ids
* FreeBSD/i386 port added
* UnixWare and Solaris updates
* Better support for tracing multithreaded processes in Linux. Please note
that programs using pthread will still hang under strace due to signal
games they want to play.
Where can I get it?
-------------------
If you are running Debian unstable strace 4.4 source and i386 packages
will appear on mirrors later today. You can also download it directly
from the sourceforge project page, there is a link to that on the strace
homepage (http://www.liacs.nl/~wichert/strace/)
--
_________________________________________________________________
/ Nothing is fool-proof to a sufficiently talented fool \
| wichert@wiggy.net http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
reply other threads:[~2001-08-19 13:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010819150248.B1021@wiggy.net \
--to=wichert@wiggy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=strace-devel@lists.sourceforge.net \
/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