Re: [Valgrind-users] Thread names in valgrind and vgdb

2012-11-11 Thread Matthias Schwarzott
On 10.11.2012 18:24, Philippe Waroquiers wrote: On Fri, 2012-11-09 at 07:52 -0700, Tom Tromey wrote: Matthias Using plain gdb, info threads also lists these user-defined names. Matthias But valgrind and gdb+vgdb only show the thread-ids. Currently I don't think there is a way for vgdb to

Re: [Valgrind-users] Thread names in valgrind and vgdb

2012-11-10 Thread Philippe Waroquiers
On Fri, 2012-11-09 at 07:52 -0700, Tom Tromey wrote: Matthias Using plain gdb, info threads also lists these user-defined names. Matthias But valgrind and gdb+vgdb only show the thread-ids. Currently I don't think there is a way for vgdb to report this back to gdb. The thread name could

Re: [Valgrind-users] Thread names in valgrind and vgdb

2012-11-09 Thread Tom Tromey
Matthias == Matthias Schwarzott z...@gentoo.org writes: Matthias pthread_setname_np and that is implemented by calling the syscall Matthias prctl(PR_SET_NAME). Matthias Using plain gdb, info threads also lists these user-defined names. Matthias But valgrind and gdb+vgdb only show the

Re: [Valgrind-users] Thread names in valgrind and vgdb

2012-11-07 Thread Philippe Waroquiers
On Wed, 2012-11-07 at 16:54 +0100, Matthias Schwarzott wrote: Printing thread names is not a bad idea (not too sure that a lot of applications are using pthread_setname or prctl but never mind). In any case, I see several subtilities to look at. Using plain gdb, info threads also lists these