https://bugs.kde.org/show_bug.cgi?id=479191
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #2 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
On what are you running ? (processor, linux version, ...).
The difference between the first and second vgdb trace is that in the second
case,
the threads are blocked in a system call, and vgdb has to do more complex
operations to
wake up valgrind.
Also, you launch valgrind with --vgdb-error=0.
This allows to do some gdb/vgdb operations before startup.
What is the reason for this in your case ?
If you put two -d options, vgdb will output more debugging info.
Also, you might add debugging options (-v -v -v -d -d -d) at valgrind side to
see what happens there.
--
You are receiving this mail because:
You are watching all bug changes.
