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

[Groleo Marius]

On Tue, Sep 22, 2009 at 11:36 PM, Julien Vanegue
<julien.vanegue at gmail.com>wrote:

>
>> 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 :)
>

Well the above 2 simple C files were compiled with -O0 (disable all
optimizations) and as I said
the "char path[7]={0,};"  failed  while "char path[8]={0,};" was ok,
regardless if testcrypt() had any parameters.




>
> Julien
>
> _______________________________________________
> eresi-dev mailing list
> eresi-dev at lists.einherjar.de
> http://lists.einherjar.de/mailman/listinfo/eresi-dev
>
>


-- 
Regards, Groleo!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.einherjar.de/pipermail/eresi-dev/attachments/20090922/bccab8e4/attachment-0001.html>