This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: add an option, let the systemtap doesn't check whether the probe point is at the start of an assembly instruction
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: peng yu <yupeng0921 at gmail dot com>
- Cc: systemtap at sourceware dot org
- Date: Mon, 16 Jul 2012 11:33:04 -0400
- Subject: Re: add an option, let the systemtap doesn't check whether the probe point is at the start of an assembly instruction
- References: <CAG3TDc2o555trzG3BT7t89xqPD+VL-RWWVfzNp+hQhS3qT6n1Q@mail.gmail.com>
peng yu <yupeng0921@gmail.com> writes:
> [...]
> But sometimes, I really
> need to probe an address which is not at the start of a statement. [...]
> [...] I think it is useful if the stap command can accept a
> new cmdline option, let it don't do the address valid check. So such
> systemtap script can work: "probe kernel.statement(0xc041df99)".
Thanks for the patch. But before we dig into that further, have you
tried
# stap -g 'probe kernel.statement(0xc041df99).absolute {}'
?
- FChE