On 07.11.2012 16:54, Matthias Schwarzott wrote: > Hi! > > I wonder if it would be good to have valgrind remember the names of the > threads. > Our application sets the name of the threads using I finally managed to create a ticket with the current version of the patch attached:
https://bugs.kde.org/show_bug.cgi?id=322254 Remaining open issues: * The thread info tid+name is not printed if it is still the same thread but the name changed. * The thread info is not printed if it is a different thread, but the tid is the same (see https://bugs.kde.org/show_bug.cgi?id=322258). * The first thread is called "main", but it could get the name of the real executable (as without valgrind). * The gdb test stdout filter does not like the changed output of "info threads". * For drd/helgrind, copy the name over to the thread structures of the tool (to also keep it after a thread has terminated). 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
