similar to: Duplication in dtrace''s forceload entries in /etc/system

Author: bmc Repository: /hg/zfs-crypto/gate Revision: 213bfe03af413cdf71c523fb076aaa65a6306a7e Log message: 6256581 System got a hang or a panic with dtrace+kmdb 6264573 unanchored dtrace_getpcstack is rather imprecise toward function end 6289517 dtrace doesn''t like fd_intr anymore 6291378 dtrace helpers can interfere with the use of kmdb 6295554 dtrace doesn''t report

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

Hey, Do you guys think that is a good idea to have a manual page for each provider with a complete description of what probes are offered ? Found some already under 7D category: dtrace dtrace (7d) - DTrace dynamic tracing facility fasttrap fasttrap (7d) - DTrace user instruction tracing provider fbt fbt (7d) - DTrace function boundary tracing provider

OK, I''ve been fritzing around with something I noticed last night, thinking that I understood what was going on, but now it''s getting confusing again. A system that has been running for a couple of months had a hole in the probe ID list near the end in the middle of the fbt probes. And then a couple of syscall probes were stuck in the hole. It looked like this: ... 40311

I''d like to see if we can use DTrace to as the kernel implementation of the BSD systrace security policy system (http://www.systrace.org). I don''t really want to port systrace to Solaris because I think with DTrace we already have all the necessary in kernel hooks to do this. With systrace you express things like: "httpd can bind to port 80 but not any other port, it

Author: ahl Repository: /hg/zfs-crypto/gate Revision: a2677fc0a5fb6895ed56fc4698646ece44978a48 Log message: 4970475 There should be a stackdepth equivalent for userland 5084954 value of dip can be incorrect in autovec 6181505 dtrace sysinfo:::modload probe does not fire when using ''modload'' 6265417 schedctl-yield isn''t listed in sdt_subr.c 6272558 gcc and dtrace

Hi All, One of the customer is seeing the following error messages. He is using a S10U1 system with all latest patches. Dtrace script is attached. I am not seeing these error messages on S10U2 system. What could be the problem? Thanks, Gangadhar. ------------------------------------------------------------------------ rroberto at njengsunu60-2:~$ dtrace -AFs /lib/svc/share/kcfd.d dtrace:

Hi, I''m posting a question hoping someone will know the answer off hand thereby reducing my search time. :-) With USDT probes, the tracepoint is only installed by libdtrace itself, never by the drti ioctl. So whenever I run a program with an USDT probe, no tracepoint is installed. Only after I run the dtrace command the tracepoint is actually installed on the victim process. My question

Hello, I''ve done this several times in the past but a co-worker is having problems getting anonymous tracing to work: dtrace -A -m su and we see updated /kernel/drv/dtrace.conf and fbt and dtrace forceloads added to /etc/system. Upon reboot the following errors occur (note that we are running snv_66): {0} ok boot disk Boot device: /pci at 0/pci at 0/pci at 2/scsi at 0/disk at 0 File

Author: ahl Repository: /hg/zfs-crypto/gate Revision: b1ab97f77b0ad2a4fe2a43d9c5aac7259840bb90 Log message: 6370454 dtrace should support USDT probes in static functions Files: update: usr/src/lib/libdtrace/common/dt_dof.c update: usr/src/lib/libdtrace/common/dt_link.c update: usr/src/lib/libdtrace/common/dt_provider.c update: usr/src/lib/libdtrace/common/dt_provider.h

How would I determine the address of the ulwp_t structure for the current thread of a process from a 32-bit i386 executable looking at a 32-bit executable? (This is in support of a fix for 6593259: "libdtrace should prefer pid probes to breakpoints".) For example, if I compile the following code 64-bit snippet, I can get that address from 32-bit or 64-bit executables:

Is there a trick to listing available providers? I can''t find it.

If I use a simple dtrace script such as this: fbt::somefunc:entry{self->trace=1;} fbt::somefunc:return{self->trace=0;} fbt:::entry{} fbt:::return{printf("%lx", arg1);} then it will descend to whatever depth is necessary If I want to limit it to say 3 functions deep, how can I do that? The quick answer I want to use is to do "self->depth++" on each entry and then

i am doing reads and writes to /dev/rdsk/c0t2d0s4 using dtrace to see how much time it took for ssdread and ssdwrite. It shows very small number 4 or 5. #pragma D option flowindent syscall::pread:entry { self->trace = 1; self->size = arg2; } syscall::pwrite:entry { self->trace = 1; self->size = arg2; } fbt:ssd:ssdread:entry /self->trace/ { self->start = timestamp;

Hi Nils, all, I tried the ''FBT-trick'' suggested below by Nils and (of course :-) ) it works and gives me a pile of output. Good enough to show that indeed Linux application behavior is not totally opaque, good enough to for instance show that ''system call mapping'' is taking place. I wonder, is there any documentation available for lxsyscall module ? To learn

Hi all, What is the correct way to give one non-root user the ability to use DTrace with providers running in a process by another user? Through the Web Stack project and some work by Ludovic Champenois and Nasser Nouri, we have done a bit of work to bring together parts of chime, the Web Stack Apache, Ruby and PHP providers, and stuff reused from the DTrace toolkit. It''s in

Hello all, I saw this question about a year back in the archive[1], but with no final answer. I would like to trace shmget calls and also get the id of the shared memory segment. That script looked like[2], but we dont get the id since arg1 is the errno value. How do i access the shm id, i would need this to debug a customer problem but i don''t have time to learn it the hard

There is a Slashdot discussion today titled "Cambridge Researcher Breaks OpenBSD Systrace". Slashdot anonymous member has a comment "Even Sun''s Dtrace might be vulnerable." I don''t think it is. Comments? Exploiting Concurrency Vulnerabilities in System Call Wrappers http://www.watson.org/~robert/2007woot/2007usenixwoot-exploitingconcurrency.pdf Abstract

Hi, I was going through the implementation of the fasttrap provider. I found that when displaced execution happens (ie., when the instruction traced is being executed out of the scratch space) if an asynchrnous signal comes we need to defer the delivery. Can somebody explain why this is necessary and how is it implemented? Thanks in advance Saravanan S -------------- next part -------------- An

Hey, Im able to reproduce a crash from plockstat everytime Im tracing a JVM pid. I do recall a problem related with this one, but not clear if this has been fixed in U3 or is it planned for U4 ? Any BugID opened for this stack trace: > ::stack libc.so.1`strlen+0x50(100003faa, ffffffff7ffff5c8, ffffffff7eca1114, ffffffff7fffec79, 0, 100003fa9) libc.so.1`snprintf+0x88(ffffffff7ffff8f0, 0,