I have a user that was adding some rather expensive probes to library
code.
Their code ended up factoring in such a way that the main line code
had IS_ENABLED()
tests guarding calls to another function that did the real work of
argument construction
and calling the actual dtrace prob
Yi wrote:
> Hi,
>
> I know how to trace the number of bytes read/written by a program by summing
> the argument of that read/write syscall. However, the way the OS services
> read/write calls is in blocks. I wonder if it's possible to trace the actual
> number of blocks read/written caused by th
Hi,
I know how to trace the number of bytes read/written by a program by summing
the argument of that read/write syscall. However, the way the OS services
read/write calls is in blocks. I wonder if it's possible to trace the actual
number of blocks read/written caused by the syscalls?
--
This
Terri,
Yes, it would be great if you mention the new features of NetBeans DTrace GUI
Plug-in in your blog.
Thanks,
__Nasser
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
I could add some information to the blog I posted this morning about 6.5
if you think it would be a good addition.
http://blogs.sun.com/ontherecord/entry/a_href_http_netbeans_org
-terri
Nasser Nouri wrote:
A new version (0.4) of NetBeans DTrace GUI plug-in is ready for download from
NetBean
Robert S. Horrigan wrote:
> Does anyone have any recommendations on how to capture using DTrace?
>
>>
>> Basically our client is tuning a Web Server 7 instance, and theApp team has
>> asked the sys admin to
>> observe the Acceptor threads. They want to see how many they have, how
>> many are act
Hi,
The TclDtrace binding implementation is complete now[1]. While focus is on
writing demos more complicated than the sample program[2], it would be nice
to hear some opinions on the API[3] or implementation[4]. Anyone willing to
test is welcome with his success/failure reports, bug reports[5]
