https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #4 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to David Hagood from comment #3) > I tried with the version of Valgrind delivered with Ubuntu 14.04 (3.9), and > had the problem (hence why I went to 3.12). If you think it's worth it, I am > willing to try 3.11 - I couldn't see any sources for download, a link would > be appreciated. If this is easy for you, doing a test with 3.11 can eliminate a regression in 3.12, while 3.9 is too old. You can get it: http://www.valgrind.org/downloads/valgrind-3.11.0.tar.bz2 Of course, the best would to be have a small reproducer. > > I did try with fair_sched=yes as well as =no. > > From what I can see, there are no other threads within Valgrind running > (i.e. attaching gdb to Valgrind and doing a "info threads" shows only the > one thread). At least old versions of gdb could not properly detect the several threads running in a 'valgrind process' : on debian, gdb 7.7 only sees one thread after attaching, while gdb 7.12 can see all threads of a simple multi-thread program. What you can do after attaching (even to one thread) is to print all the thread status and exit reason: (gdb) p vgPlain_threads[1].status $3 = VgTs_WaitSys (gdb) p vgPlain_threads[1].exitreason $4 = VgSrc_None (gdb) p vgPlain_threads[2].status $5 = VgTs_Empty (gdb) p vgPlain_threads[2].exitreason $6 = VgSrc_ExitThread (gdb) p vgPlain_threads[3].status $7 = VgTs_Empty (gdb) p vgPlain_threads[3].exitreason $8 = VgSrc_ExitThread (gdb) p vgPlain_threads[4].status $9 = VgTs_Empty (gdb) p vgPlain_threads[4].exitreason $10 = VgSrc_ExitThread (gdb) p vgPlain_threads[5].status $11 = VgTs_Empty (gdb) p vgPlain_threads[5].exitreason $12 = VgSrc_None .... (or do print e.g. the first 10 entries doing p vgPlain_threads[1]@10 and then grepping the output for status and exit reason. An empty/none entry means never used. > > WRT 361516: The program(s) being inspected are not being killed via a signal > - they are terminating naturally. -- You are receiving this mail because: You are watching all bug changes.
