Naveen N Rao

Oh, I probably should have explained better. The problem actually shows up at runtime and not while building bcc itself. In this case, it is with test_uprobes.py: ``` # /root/bcc/build/tests/wrapper.sh...

Sure. It looks like @vmg wrote much of this code. @vmg do you have ideas on how best to address this?

@mprzybylski you can put in a `sleep()` in `tests/python/test_uprobes.py` and check `/sys/kernel/debug/tracing/uprobe_events` to see which library is being picked by bcc.

I thought of using the aux vector to figure out the hardware capabilities before picking up the right library, but with 32-bit and 64-bit libraries, that may not be enough....

This would be good to have. Here is a curtailed entry that I imported to `khal`, but doesn't display in `khal`: ``` BEGIN:VCALENDAR VERSION:2.0 PRODID:-//PIMUTILS.ORG//NONSGML khal / icalendar //EN BEGIN:VEVENT...