This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: systemtap to trace source of syscall error?
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Adrien Kunysz <adrien at kunysz dot be>
- Cc: "Richard W.M. Jones" <rjones at redhat dot com>, systemtap at sources dot redhat dot com
- Date: Mon, 20 Dec 2010 10:11:42 -0500
- Subject: Re: systemtap to trace source of syscall error?
- References: <20101219180836.GA14864@amd.home.annexia.org> <20101219183041.GA8740@baltika>
adrien wrote:
> [...]
> If you have a reliable reproducer, I would suggest divide and
> conquering with something like this:
>
> global testnr = 1
>
> probe kernel.function("do_utimes@*.c:139"),
> kernel.function("do_utimes@*.c:142"),
> [add more checkpoints here as you dig deeper]
> {
> printf("passed test %d, now at %s\n", testnr++, pp())
> }
Yikes, that should be kernel.statement, not kernel.function. I wonder
if we should get stap to warn for a line-number-laden kernel.function
probe spec.
- FChE