CRiSP Blog

Dtrace weirdness (really, me weirdness)

I spent much of the week chasing an issue in why the usdt/c example
wouldnt compile or build. I hadnt really changed anything in this area, yet
an invalid simple.o was being created (invalid in an ELF sense).

I tracked down a partial reason to be that in calling libelf.a, the enum's
we pick up from the elf.h header file(s) didnt agree with what libelf.a was
expecting. (Very weird - looks like the Solaris elf header and Linux header
dont agree).

What I dont understand is why this suddenly hit. I am thinking one of my
Ubuntu updates caused a discrepancy to the header and libraries, and I have
been chasing my tail.

Early on in dtrace/linux evolution, I did a bunch of work to dt_link.c
to all USDT probes to work, and I was happy with my changes. Just now, I reverted
all of them, and my USDT problems went away.

Something fishy is going on here - so I urge caution when I do the next distro.
It maybe my build environment is polluted/broken and that may cause differences
between what I observe and what dtrace users see on their systems.



Post created by CRiSP v10.0.2a-b5887


Read more http://crtags.blogspot.com/2010/09/dtrace-weirdness-really-me-weirdness.html

Testimonials

"After looking for a good text editor for UNIX for several years I finally found one that met my needs in CRiSP. I have used vi, emacs, xcoral (not to mention edt, teco, brief, tpu, etc, etc.) but prefer using CRiSP for two main (but not exclusive) reasons. First is the language sensitive syntax colorization and second for it's ease of use (brief editor like functionality)."

paypal_horiz