This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: Controlling probe overhead
- From: "Stone, Joshua I" <joshua dot i dot stone at intel dot com>
- To: <fche at redhat dot com>
- Cc: "David Smith" <dsmith at redhat dot com>, "SystemTAP" <systemtap at sources dot redhat dot com>
- Date: Mon, 12 Mar 2007 17:01:32 -0700
- Subject: RE: Controlling probe overhead
fche@redhat.com wrote:
>> Right now I'm treating too much overhead as a hard error, but we
>> could make it more like a forced exit instead. This way the end
>> probes would still run, so if you have a long-running script that
>> aborts suddenly due to overhead, you can still get some sort of
>> report out of it. [...]
>
> Another possibility is to leave it as a hard error, but introduce
> "error" probes. It would be an end probe that runs iff we are exiting
> in ERROR state: kind of between "end" and "never".
I like this idea.
And since I like convoluted corner cases -- what do you do if an end
probe triggers an error?
Josh