I accept both, either in man page or in dtrace usage().
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
The error message without this bug would have identified the DIF
offset which could then be used to manually determine the line of the
source file. Doing it programmatically is a long-standing RFE.
Adam
On Dec 2, 2008, at 10:43 PM, Dan Mick wrote:
> OK. I don't know if it is or not, but Jim
OK. I don't know if it is or not, but Jim ran into it on what seems like a
valid D script. I'm guessing his problem was because of the multi-dimensional
aggregation index? Can the error message indicate the D line that caused the
problem?
Adam Leventhal wrote:
> You can't. Right now this is
Hi Matthew,
Your choice are to unroll a loop and use predicates to know when
you've reached the end condition or to save state in global variables
and use a tick probe to iterate through the list. If you need more
guidance, feel free to ask, but you may be able to find an example of
this i
You can't. Right now this is a limitation of the compiler. If it's a
common use case we can likely find a solution.
Adam
On Dec 2, 2008, at 10:25 PM, Dan Mick wrote:
> How does one make the compiler generate runnable code with such D
> input?
>
> Adam Leventhal wrote:
>> Hey Jim,
>> I was ab
How does one make the compiler generate runnable code with such D input?
Adam Leventhal wrote:
> Hey Jim,
>
> I was able to reduce this to a simpler case:
>
> # dtrace -n BEGIN'{ foo[1, 1, 1, 1, 1, 1] = 1; }'
> dtrace: failed to enable 'BEGIN': DIF program content is invalid
>
> This failed bec
I have a provider that allows me to look at some application-specific
data structs for SJS Web Server 7. The problem I'm finding is that
some of the data is stored in a short linked list and I don't see any
way, without the unimplemented "for" or "if" constructs in dtrace, to
trace those d
Hi Diego:
Interestingly this same issue came up on another alias today.
Amjad Khan responded with the following detailed and useful
suggestion. Hope this helps you as well.
When a zone is created in the kernel there is a default set of "safe"
privileges which are used as a mask for all proce
Start with iostat. It's simple, and provides an average of service times
for disk IOs (iostat -xnz 1, the asvc_t column is average service times
in milliseconds). As Jim Litchfield pointed out in a previous thread,
keep in mind it is an average, so you won't see nasty peaks, but if the
average is b
Hello,
I have solaris 10 machine and I was trying out dtrace. I downloaded some
scripts (iotop, errorinfo, prustat) and they all show this error:
dtrace: invalid probe specifier
along with other errors such as:
probe description dtrace:::BEGIN does not match any probes (iotop)
probe description
In order to get more information on IO performance problems I created the
script below:
#!/usr/sbin/dtrace -s
#pragma D option flowindent
syscall::*write*:entry
/pid == $1 && guard++ == 0/
{
self -> ts = timestamp;
self->traceme = 1;
printf("fd: %d", arg0);
}
fbt:::
/self->
11 matches
Mail list logo
