Tracecap plugin issues

86 views
Skip to first unread message

pungu

unread,
Jan 11, 2012, 11:55:00 AM1/11/12
to BitBlaze User Discussion group
Hi

We were able to successfully compile the tracecap plugin and run it in
my environment. I observed that the size of the new compiled
tracecap.so is smaller than the one available in the default temu
distribution. Though this is not the problem.

The problem is that when with log_external_calls = yes

the trace and the "trace.calls" files get created but are empty.
-rw-r--r-- 1 root root 0 2012-01-11 08:04 neelam.trace
-rw-r--r-- 1 root root 0 2012-01-11 08:04 neelam.trace.calls
-rw-r--r-- 1 root root 127578 2012-01-11 08:05 neelam.trace.functions
-rw-r--r-- 1 root root 21 2012-01-11 08:04 neelam.trace.netlog



When i did the same test with the default tracecap.so file from the
temu distribution, it works absolutely fine.

Any help will be appreciated.

regards
Neel

Stephen McCamant

unread,
Mar 16, 2012, 4:04:47 PM3/16/12
to bitblaz...@googlegroups.com
>>>>> "JW" == jaewon6867 <jaewo...@gmail.com> writes:

JW> where did you get the source code?
JW> I keep seeing posts on the internet saying that they compiled the
JW> tracecap but wasn't able to get anything

Our various releases of BitBlaze software are listed on the web at:

http://bitblaze.cs.berkeley.edu/release/index.html

For most purposes we recommend the TEMU 1.0 release, which contains
only a binary version of the Tracecap plugin.

However we've also made a release of some additional source code
related to TEMU and Vine. This is not a complete packaged release like
TEMU and Vine 1.0, but it includes source for some additional
functionality that may be useful, including for the Tracecap plugin.

We have a web form you may use to request access to this release; it's
linked to from the page I mentioned above, or you can get to it
directly at:

http://aerie.cs.berkeley.edu/release/request.php

Hope this helps,

-- Stephen

Alex Bazhanyuk

unread,
Apr 5, 2012, 2:57:27 AM4/5/12
to bitblaz...@googlegroups.com
if you enable log_external_calls then you getting only call-trace: neelam.trace.calls
Reply all
Reply to author
Forward
Message has been deleted
Message has been deleted
0 new messages