|
From: Tom H. <th...@cy...> - 2005-01-26 13:27:25
|
In message <41F...@hl...>
mic...@hl... wrote:
> I am having difficulties using the automatic db attach feature in a
> multithreaded program. Valgrind asks me to attach the debugger, but
> the other threads seem to continue running in the background,
> producing new error messages. Needless to say, that my program doesn't
> work at all as expected if just one thread is suspended.
Is this using 2.2 or CVS code? Not that I think it matters much as
although the threading model is very different, valgrind controls the
scheduling in both cases and should be frozen while in the debugger.
> Could you add a flag so that valgrind suspends all threads from
> continuing, while the program waits for user input/tries to start gdb ?
Only one thread runs at a time under valgrind and while that thread
is in the debugger no other thread will be scheduled to run.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|