9 Aug
2004
9 Aug
'04
12:53 p.m.
Hi,
On Mon, 9 Aug 2004, Vincent Bremaud wrote:
If this doesn't work, the thing I would do would
be to launch mozilla in
gdb, wait for the SIGSEGV signal, and see in which line in the source of
Mozilla is the problem. Maybe a variable contains a reference to the
resource causing the problem.
Alternatively, use ulimit to allow for core dumps (ulimit -c size),
and run gdb on the core file after a crash.
Helped me find a problem with a proprietary product a few months
back.
Greets Eric