This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Trace syscalls
- From: "Rus-Rebreanu Alin-Florin" <netblock at gmail dot com>
- To: systemtap at sourceware dot org
- Date: Mon, 24 Mar 2008 21:43:21 +0200
- Subject: Trace syscalls
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=gYhHdbOQEFHr5zwh6tw4MZbd7Uf+RmBPdaCpaT1Iajw=; b=DDS7ALSD4ojfL4j2cxCTrpE1oFg+vsxC0F3h0FzF4nkDRxwM22lOvRjkl4mYOn+g+Nc/Eh6Tv0FaT5TvNEurEl5mPWcJRT9kcB3nVWyGtOM3711elDpNStM07CDVDj2XSUhcTC+LQcStVWW71Hao4OG7DLjw5TvLFGqVQW4XYkk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=AXCFwmp1P9n1yJhxZsZKuiqdMzCJgGNM8nfHjFQ+rf1NbC2DQKcbe6iB95HmU2Th3h5e2tahxNf4vlp4nOn7pICE4Jt+hhRNZnB9Stk4GMUvLaWd9L4/Nlqr3jgkW6BhwOp0EAOT/b2GEoSkBuNQiSB8XciYmIVHNobvh+giqis=
Hi,
i'm quite new with systemtap but it seems as a wonderful way to trace
syscalls. i want to trace for example sys_write in such a way that it
would print the internal path of the sys_write syscall. such as:
entering fget_light()->exit fget_light()->entering
file_pos_read()->exit file_pos_read() or even follow the path into
those functions.
do i have to write a probe for every single kernel function i want to
trace? or is it a simpler way to trace the path through a syscall?
i tried , and it's almost what i want :
probe kernel.function("*@fs/read_write.c"){
printf("%s->%s\n",thread
_indent(1),probefunc())
}
probe kernel.function("*@fs/read_write.c").return{
printf("%s->%s\n",thread_indent(1),probefunc())
}
but this adds probes to all the functions in the read_write file, and
i'm only interested in read or write syscalls, but entering every
function of the syscall
Some "pointers"?
--
"In a world without walls and fences, who needs windows or gates? "