valgrind-users

[Valgrind-users] Thanks, compilation problem, Emacs mode?

[Andreas O. <oe...@oe...>]

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

Re: [Valgrind-users] Thanks, compilation problem, Emacs mode?

[Arnaud D. <arn...@ge...>]

----- Original Message -----
From: "Andreas Oesterhelt" <oe...@oe...>
To: <val...@li...>
Sent: Tuesday, May 06, 2003 6:50 PM
Subject: [Valgrind-users] Thanks, compilation problem, Emacs mode?

> 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?
> ,-)

Try that in your .emacs:

;; from Ole Aamot (ol...@gn...)
;; Valgrind (memory debugger for x86 GNU/Linux):
;;  ==1332==    at 0x8008621: main (vtest.c:180)
;; Currently this regexp only matches the first error.
;; Thanks to Hans Petter Jansson <hp...@xi...> for his regexp wisdom.
(setq compilation-error-regexp-alist
  (append compilation-error-regexp-alist
    '(("^==[0-9]+==[^(]+\(\\([^:]+\\):\\([0-9]+\\)"
       1 2))))

Regards,

[Valgrind-users] Re: Emacs mode?

[Andreas O. <oe...@oe...>]

Hi Arnaud,

On Tue, 6 May 2003, Arnaud Desitter wrote:

> ;; Currently this regexp only matches the first error.
> ;; Thanks to Hans Petter Jansson <hp...@xi...> for his regexp wisdom.
> (setq compilation-error-regexp-alist
>   (append compilation-error-regexp-alist
>     '(("^==[0-9]+==[^(]+\(\\([^:]+\\):\\([0-9]+\\)"
>        1 2))))

thanks a lot! This works nicely when called from the
compilation-mode-hook, and despite the comment it works
for all lines matching the RE, not just the first one.

Regards,
--Andreas