similar to: RFE idea: make #defines from sys/fault.h available by default

Hello, everyone I am a newbie of DTrace and OpenSolaris. Just wondering is it possible to trace every memory read/write of a specific process given the pid? Basically speaking, I want to record the virtual addresses being accessed by the process, using which I will try to do some online analysis. If DTrace does not support this type of instrumentation, will other tools in OpenSolaris help me

Hi all, There''s a dead thread about this back at http://forums.sun.com/thread.jspa?threadID=5075157, but it would be really nice to have support for if/else control flow in actions. Reasons: 1. The ternary operator ?: is already there (though it doesn''t let you do anything with side effects) 2. The user can already write arbitrary and expensive non-cacheable predicates if

This came up as an RFE during the conference (I believe it''s been logged as "4012008: brendan() action needed for DTrace Toolkit".) As everyone here is aware, DTrace is not quite as user friendly as it could be. For the uninitiated, it can be confusing to run a DTrace script and not see the expected output. Brendan Gregg has addressed this in the DTrace Toolkit[1] by

How do I query an application to see if it supports any USDT probe points?

Hi, I''m working on some performance analysis with our database and it seems that when the file system (UFS) is mounted with forcedirectio, the IO probe are not triggered when an I/O event occurs. Could you confirm that ? If so, why ? Seb -- This message posted from opensolaris.org

Hi All, I''ve got a problem when I have USDT probes in a static library and in the application code outside of the library. I build the static library containing some USDT probes, glomming everything together (ld -r) before creating the .a file to preserve the probe symbols. This all works fine. I build an application which also has some USDT probes. When I build the application which

everyone, Just out of curiosity, I did a dtrace -n ''syscall:::entry { @num[execname, probefunc] = count(); }'' and looked at the entries produced by ''rm''. I see everything that rm did, *except* the unlinkat - which is unfortunate because I want to trace which processes have deleted which files. So - does dtrace contain unlinkat as a probe for a system call?

Hi, I have used dtrace in the past for diagnosing IO/filesystem related issues. So I am a bit familiar with dtrace scripts Now I want to diagnose performance problems in the java area. May be memory leak etc. The hotspot provider is not present. How can I get them? Does someone have any further advice? regards Hans -- This message posted from opensolaris.org

I''m not sure if this is the right place for the question or not, but I''ll throw it out there anyways. Does anyone know, if you create your pool(s) with a system running fishworks, can that pool later be imported by a standard solaris system? IE: If for some reason the head running fishworks were to go away, could I attach the JBOD/disks to a system running snv/mainline

What''s going on? # dtrace -s iotime_all.d 100 dtrace: failed to enable ''iotime_all.d'': DIF program content is invalid The errant script.... #pragma D option quiet BEGIN { stime = timestamp; io_count = 0; } io:::start /args[2]->fi_pathname != "<none>"/ { start[pid, args[2]->fi_pathname, args[0]->b_edev, args[0]->b_blkno,

Hi: I''m running Indiana (OpenSolaris developer preview) under parallels in OS X 10.5.1. I can consistently get Solaris to hang. Doing a dtrace -n pid\$target::malloc:entry''{@=count()}'' -c ls will consistently hang Solaris. Basically doing anything with PID provider with the -c option seems to hangs Solaris. Only way to recover is to stop and start Parallels desktop.

I''m pleased to pass along news that the Mac OS X DTrace port has been updated in 10.5.3 to fix the issue that caused timer based probes not to fire in the presence of certain untraceable applications. http://blogs.sun.com/ahl/entry/apple_updates_dtrace A big thank you to the folks at Apple for addressing the problem. Adam -- Adam Leventhal, Fishworks

I''m running OpenSolaris 2008.05 in VirtualBox on a Windows XP host. Playing around with various probes, I found that trying to load any probe associated with bdev_strategy dumps core. I can think of one or two likely and reasonable causes for this, but am assuming it''s undesirable behavior. Anyone know what''s happening here? -- This message posted from

I''d like to prepend TRACE_ to the macro names generated by dtrace -h. For example, change POSTGRESQL_LWLOCK_ACQUIRE(arg0, arg1) to TRACE_POSTGRESQL_LWLOCK_ACQUIRE(arg0, arg1) and still keep postgresql as the provider name. The reason for doing this is to make it clear that the macros are used for (D)tracing. In this particular case, without TRACE_, it appears like the macro is used

Starting from this thread: http://www.opensolaris.org/jive/thread.jspa?messageID=118786&#118786 I would love to have the possibility to set an ISCSI alias when doing an shareiscsi=on on ZFS. This will greatly facilate to identify where an IQN is hosted. the ISCSI alias is defined in rfc 3721 e.g. http://www.apps.ietf.org/rfc/rfc3721.html#sec-2 and the CLI could be something like: zfs set

N_conreq:entry { self->x=1; calledaddr=(struct xaddrf *)arg3; callingaddr=(struct xaddrf *)arg4; trace(calledaddr->link_id); tracemem(calledaddr->DTE_MAC.lsap_add, 80); trace(callingaddr->link_id); tracemem(callingaddr->DTE_MAC.lsap_add, 80); } 0 -> N_conreq 255

Hi , I have c++ server application in solaries 10 . Day by day memory usage is growing i try to find memory leaks with MDB and DTRACE and no leaks found. how can we find reason for growing memory , can we know which memory sigment is cause for growing memory usage Thanks in Advance. Rao -- This message posted from opensolaris.org

Hi, Created a zpool with 64k recordsize and enabled dedupe on it. zpool create -O recordsize=64k TestPool device1 zfs set dedup=on TestPool I copied files onto this pool over nfs from a windows client. Here is the output of zpool list Prompt:~# zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT TestPool 696G 19.1G 677G 2% 1.13x ONLINE - When I ran a

Greetings, is there a way to specify probes and other dtrace operations via command line parameters, like " BEGIN { usr_exec=$$1; usr_syscall=$$2; } syscall::usr_syscall:entry /execname == usr_exec && guard++ == 0/ { ... " [this does not work] This would make it possible to create "generic" dtrace scripts. Otherwise, some shellscript with sed-magic would

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i''m trying to use the nfsv3 provider on S10U6, with the following simple script: #! /usr/sbin/dtrace -s #pragma D option quiet nfsv3:::op-read-start { printf("%s\n", args[1]->noi_curpath); } however, when running it, i get the following error: dtrace: failed to compile script ./nfs2.d: line 5: failed to grab