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

[Groleo Marius]

Hi,


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

> Hi Marius
>   Btw, Can you reproduce the test in testsuite/tracing/ ? (this is known
> to work)
>
Yes, I started from host.c and removed code till I hit a non-traceable
binary;

----------------------------------
Traceable
#include <stdio.h>

void  testcrypt()
{
}

int main()
{
  char path[8]={0,};
  putchar(path[0]);
}


---------------------------------------------------------------------------
Non-traceable
#include <stdio.h>

void  testcrypt()
{
}

int main()
{
  char path[7]={0,};
  putchar(path[0]);
}
--------------------------------------------------------------------------


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.







>
> If you want to contribute a symbol mangling function to make etrace support
> C++ binaries, I could tell
> you easily how to integrate it into libelfsh :) I can remove the 0 args
> limit if you have an interest.
>
> Let me know
>
>
I would like to try and see how far I could get.



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