|
From: Michael P. <md...@tr...> - 2006-06-17 01:34:10
|
Timothy B. Terriberry writes: > The thing that makes it odd, and the only reason I'm bothering to report > it at all was that the problem occurred with 100% reproducibility with > valgrind 3.1.1, and has never occurred with 2.4.0. Similar problems show up with the fglrx driver when debugging OpenGL apps under gdb: if the debuggee stops at particular places, it locks up the machine. I haven't tried it with other drivers, so I don't know if the behavior is specific to fglrx or not, but I doubt valgrind has any role other than to trigger it. Michael Poole |