|
From: Ron V. I. <van...@ca...> - 2006-03-08 19:54:52
|
First, let me start off with saying valgrind is one of the most wonderful pieces of open source software I have used, ranking right up there with g++, in making my day to day work livable. I do have one small itch relating to valgrind and that is the fact that you cannot use both db-attach and trace-children at the same time. On my project, we currently run on larger SGI MIPS 64processor systems and are migrating to multi processor Xeon systems. On MIPS, we use purify to debug our simulation software which often requires 40+ processors to run. Purify supports what they call Just-In-Time (JIT) Debugging which pops up a dbx session in another window whenever a bug is encountered. One can also have this occur only on corrupting errors rather than just on non corrupting errors such as uninitialized memory reads. The JIT feature of purify is very useful since our large simulation often has memory issues that are much easier to debug if a debugger is provided at the moment of the error occuring. I searched the mailing list archives and saw this question come up in August of 2005 and Tom Hughes supposed that the problem with db-attach and multiple children is a focus issue with the terminal. Purify solved that by simply popping open a new xterm with dbx for each child that encountered a problem. This could, of course, be done using ddd or some other GUI debugger as well. This certainly solves the focus issue and, if that is the only problem, it would be nice to have this fixed. With a bit of direction, I could try to implement this myself but I have not even begun digging around in the source code yet... --Ron |