309718 - Unable to run Firefox with --trace-malloc

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Boris Zbarsky [:bzbarsky]]

I tried to run Firefox with --trace-malloc set (to debug bug 309467), but it
seems to fail.  The browser window never appears, CPU usage goes to zero after a
bit, and breaking in gdb at this point shows us always under an fread(). 
Starting up Firefox without the --trace-malloc command-line option works fine.

Seamonkey builds, both GTK1 and GTK2, built from the same exact source, work
just fine with this command-line option.

I know we do have a tinderbox that runs trace-malloc with Firefox, which is why
I tried the GTK version thing (this tinderbox builds Firefox GTK1, it claims). 
So I have no idea what's going wrong here.  But it really would be nice if I
could get our debugging tools to actually work with Firefox locally.  :(

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

This could be bug 363334 (plus gdb being confused).

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Boris, could you retest now that bug 363334 (and bug 366169) are fixed?

(I think there are still some potential crashes due to dangling library pointers, since we just hold onto the strings returned from dladdr rather than copying them, but I'm fixing that in bug 374829.)

Comment 3

[Boris Zbarsky [:bzbarsky]]

Yeah, this is no longer a problem, but now I hit crashes.  See bug 376874.