Hi Remigiusz,
sorry for the delay, I have been very busy in the last few days,
deadline coming up...
have not had time yet to look at the aggregations issue, will try to
do it soon, FWIR it should be possible to get at the aggregation
names, it's inconvenient not to have that info in the
[dtrace::aggregations] output.
On 11/08/2008, at 15:27, Remigiusz Jan Andrzej Modrzejewski wrote:
> I've realised, that a call to exec followed by a call
> to ::dtrace::grab is not really a good idea... A quick process may
> actually be gone before we grab it. Tested with /bin/true. I'm not
> all that sure of the command name - better ideas welcome.
I would suggest not worrying too much about that problem for now, it
would be a serious pain to reimplement all of tcl's [exec] in
TclDTrace...
or were you thinking of using libdtrace's dtrace_proc_create() to run
the command?
that would be useful, but I would do it in addition to [dtrace::grab],
not instead of (it is very common to want to grab a longrunning
process, as with 'dtrace -p'), e.g. [dtrace::launch] might be an ok
command name for that functionality ?
Cheers,
Daniel
--
** Daniel A. Steffen **
** <mailto:da...@us...> **
|
