On Sun, 2012-06-10 at 13:45 +0200, Christoph Bartoschek wrote: > Hi, > > how can I get a traceback of the programm currently running within > valgrind? I have a program that seems to run in an endless loop when run > under valgrind. Normal execution never seems to stop. > > I tried to run with --vgdb=full and then > > target remote | vgdb > > within gdb. > > However when I run bt I only get addresses and no function names. The above is supposed to give a readable stack trace.
A possible reason for not getting correct stack traces is GDB being launched on a wrong exec or no exec. E.g. if you do: gdb target remote | vgdb then this will not give good stack trace. You must do gdb your_executable_here target remote | vgdb If the above is not the reason, then some more info might be useful (which V version, which gdb, which os, ...). And of course, a small reproducer always helps a lot ... Philippe ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
