[eresi-dev] Is etrace able to trace (GCC)c++ simbols ?

[Julien Vanegue]

>
>
> Both were compiled with:
> gcc -c tracer.c -o tracer.32.o -I /libstderesi/include -I /librevm/include
> -I /libelfsh/include -I /libasm/include -DERESI32 -I /libaspect/include -I
> /libedfmt/include -I /libmjollnir/include -gdwarf-2 -fno-stack-protector
> -fno-default-inline -O0 -g
>
> See the -O0. I hope the gcc won't optimize anything.
>

This option surely change something on such simple binaries. Try with or
without this option and let us know of the result.

This is actually good to test those cases of etrace on super-simple binaries
and see what happens :)

(but its more interesting to try on very big binaries and try to make it run
faster :)

Julien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.einherjar.de/pipermail/eresi-dev/attachments/20090922/237e05db/attachment.html>