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

"I am a newcomer to Linux, and I was very disappointed with "standard" UNIX editors like vi and emacs. The user interface is so unfriendly and the feature set is so antiquated. I heard about CRiSP on the comp.editors newsgroup and downloaded a free demo...It's just wonderful! Thoroughly modern, easy to use, powerful, flexible; it's what a UNIX programmer's editor should be."

paypal_horiz