From: Andreas O. <oe...@oe...> - 2003-05-06 16:56:51
|
Hi, ..first of all: Thanks a lot for providing this extremely useful tool! The per-allocation stack traces saved me a lot of work debugging! Second, when compiling valgrind 1.9.6 I noticed a small problem which might either be due to a weirdness in my local setup (quite possible!) or valgrind's build process: On my glibc 2.2 system which had been correctly recognized by the configure script (#define GLIBC_2_2 1 set in config.h), compilation of coregrind/vg_intercept.c failed with some type checking errors involving struct timeval. Moving the #include <sys/time.h> statement out of its #ifdef GLIBC_2_1 resolved the issue. Third, does anyone know of a (X)emacs mode that would parse valgrind output and jump to the right locations in the source files on click, just like the compilation mode does? If not, does anyone feel like writing one? ,-) Cheers from a happy user! Regards, --Andreas |