|
From: Patrick O. <Pat...@in...> - 2004-03-18 15:53:58
|
Hi all, I am using valgrind 2.1.0 on a Red Hat AS2.1 installation with the original Red Hat kernel 2.4.9-e.34smp for that distribution. Hardware is both a dual Xeon IBM box and a single Xeon box. The latter one has hyper threading enabled. On both machines I have managed several time to cause a kernel panic when running valgrind, or rather by aborting valgrind with CTRL-C (at least that was the impression I got). Has anyone else ever encountered something like this? I have no doubt that this is more likely than not a kernel bug because updating the kernel to an official 2.4.22 seems to solve it, but finding a workaround in valgrind would still be very helpful: we'd like to run these machines with as little OS modifications as possible. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. |