Where should we post crash reports?

I don't always get a stack dump and an automatically sent crash report....

I just posted a brief report to the comments of the blog re: the latest First Look client. Tofu, are you reading these threads? Should we post stuff here?

Basically, the last several First Look clients have been randomly crashing with "double free or corruption" errors caught somewhere within glibc.

-Rob

I do usually read the FL threads but Steve et al should be getting on top of any heap bugs etc., which aren't specifically Linuxy.

A lot of times, SL will detect the crash and ask you if you want to send a crash report after it bombs out.

Yeah -- but with this crash, generally things freeze up and sit there until I "kill %1" (or "kill <process>" the process. Sometimes there's a stack trace that goes in next time I run SL, sometimes there's not.

I did discover that

export MALLOC_CHECK_=1

before running SL seems to make many of the freezes go away. Of course, this is a little like putting makeup on an infection What this does is tells glibc to not whine and bitch about some memory errors like double-frees. It makes for a more stable (at least, so far, in my experience) SL cruise, but ti is probably not as useful for finding bugs....

-Rob