167139 - Instrument Mozilla using Valgrind

Status: VERIFIED INVALID

(SeaMonkey :: Build Config, defect)

Description

[Christian Mattar]

Apparantly, Valgrind can detect memory leaks/corruption and instrument cache
usage, both of which are potentially large problems in Mozilla. It would
probably pay off if someone could look into this.
No idea which component, assigning to browser general

Comment 1

[Andrew Schultz]

really, this already works.  just do

% ./mozilla -g -d valgrind

on a practical level, I found it necessary to add valgrind as a separate
debugger so I could pass options (check leaks, additional suppression file, more
frames/stack, etc) to valgrind.  However, these have to be added manually to
run-mozilla.sh anyway, so I'm not sure what changes Mozilla can make for Valgrind.

==> Build Config

Comment 2

[hacker formerly known as [e-mail]]

What exactly is this bug requesting?  As Andrew pointed out, you can run
valgrind using ./mozilla -g -d valgrind and others already have.

Comment 3

[Christian Mattar]

I ran a a bugzilla query looking for valgrind before filing this bug, without
getting any results. I guess I did something wrong, since now I find lots of
bugs which Andrew et al already filed about problems detected by valgrind.

I'm sorry that I've wasted your time. :-(

Comment 4

[Jon Granrose]

verified.