Hi there! I changed writing of vgcore to make it obvious which thread has crashed. This is done by moving the thread info for the crashing thread to be the first.
See https://bugs.kde.org/show_bug.cgi?id=315199 If thread 5 crashed, gdb opening vgcore still shows thread 1 as active. After my change, thread 5 is the active one. Question: How to create a test for this? My naive idea: The test needs to run valgrind until the client app crashes, and then open vgcore in gdb to issue "bt" and check if this is the correct callstack. Regards Matthias ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
