CRiSP Blog

Typing error

Spent days trying to debug and understand dtrace with this line:


inline struct psinfo_t *curpsinfo = ((struct ps_info_t *) `curproc);


I was following the type casting and type comparing code.

Eventually I spotted a stray underscore.

Can you spot it?

Post created by CRiSP v10.0.2b-b5891


...

Read more: Typing error

Dtrace release 2010-08-30

This release includes a working kernel ctf file dump. Finally, the following
trace script should work:


io:::start
{
printf("pathname=%s\n", args[2]->fi_pathname);
}


Note the fact we are referring to fi_pathname, with no struct definition
in sight! This works because /usr/lib/dtrace/io.d is read, and this works
with the kernel ctf file.

A big...

Read more: Dtrace release 2010-08-30

Blocking on dtrace

Just having some mental blocks on dtrace. Specifically, we now
create a kernel .ctf file - but looks like this is missing something we
need, despite putting in the bufinfo_t structure in to the stubs file.

Without that, we cannot invoke args[n] because dtrace doesnt know
how to convert the struct.

Hopefully wont take too long to figure out what is...

Read more: Blocking on dtrace

Testimonials

"CRiSP is awesome, especially for anyone who likes to use Brief on the PC, and hates vi. I use it for all my code development and maintenance tasks. It's also great for editing binary files or very large files, or files which have very long lines, which cause other editors to choke."

paypal_horiz