|
From: Allin C. <cot...@wf...> - 2005-07-19 12:05:10
|
I've been using valgrind for a couple of years and am very pleased with it. An invaluable tool, thank you. One problem I've encountered recently. I have valgrind 2.4.0 installed on my machine at work (glibc 2.3.5, linux 2.6.12.2) and it works perfectly. At home I have an older system with glibc 2.3.2 and kernel 2.4.23. I've been running valgrind 2.2.0 on that system with no problems. I tried updating to 2.4.0. Valgrind configured, built and installed OK, but it won't run: it immediately segfaults (even just "valgrind --version"). (Both systems use gcc 3.4.4.) I tried getting a trace from gdb but it seems that stack is smashed right away: bt just gives "???". I tried ensuring that all the files installed by 2.2.0 were deleted in case some funny mixture of versions was happening, but this didn't help. Finally, I tried downloading the 2.2.0 source and rebuilding it: again, 2.2.0 works fine. Has anyone else seen this with 2.4.0? Does anyone have a suggestion on how I could produce a more useful report? -- Allin Cottrell Department of Economics Wake Forest University, NC |