This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

mtrace for cross compiling?


Hi all,

we're trying to hunt down memory leaks in our application.

I used mtrace() call to create a log file like

@ /usr/lib/libstdc++.so.6:(_Znwj+0x68)[0x40170ca4] + 0x232830 0x1a
@ /usr/lib/libstdc++.so.6:(_ZdlPv+0x10)[0x4016f41c] - 0x232830
@ /lib/libc.so.6:[0x402a6b2c] + 0x232850 0x16c
@ /lib/libc.so.6:(__getdelim+0xd8)[0x402a7604] + 0x2329c0 0x78
@ /tmp/idifixd.new:[0x9c08c] - 0x2329c0
@ /lib/libc.so.6:(fclose+0x1b8)[0x402a64a4] - 0x232850
@ /lib/libc.so.6:[0x402a6b2c] + 0x232850 0x16c
@ /lib/libc.so.6:(__getdelim+0xd8)[0x402a7604] + 0x2329c0 0x78
@ /tmp/idifixd.new:[0x9c08c] - 0x2329c0
@ /lib/libc.so.6:(fclose+0x1b8)[0x402a64a4] - 0x232850

Now there is a perl script called mtrace that would parse this output and
create a list of "Memory not freed:" like

   Address     Size     Caller
0x00214b78     0x94  at 0x40170ca4
0x00214c10     0x12  at 0x40170ca4
0x00214c28     0x18  at 0x40170ca4

I don't have perl on my embedded ARM system. And I guess when running mtrace
on the build host it will not use the cross tool libraries ...

Is there anyway to use the ARM libraries with the mtrace script when running
on a x86 host so I see function names in the output?

Thanks a million!

--
Steven

--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]