diegel wrote:
There is no problem. First start the bash, then execute my code.
Got through it, thanks. It was failing with bash but that was because of a different dumb error which I'm not going to describe

Quote:
Actually I plan to look at newer firefox versions later.
To each his own
Quote:
In my opinion there is absolutely nothing stupid with it.
We have widely varying opinions on that subject !
Quote:
As I wrote before, I found an optimizing problem in the javascript code. All previous Irix firefox 2 versions build with at least -O2 has this bug. This was a reason why firefox crashes. I don't expect it doesn't crash anymore, but I experienced it crash much less than before.
You've probably made a significant step forward. With javascript turned off I have LOT fewer crashes. There's also this one, if you want to look for bugs :
Code:
Assertion failed in file "../../libC/lang_support/throw.cxx", line 1618
WARNING: core: firefox-bin: PID 57254, failed to write a text area (core file deleted)
moz_run_program[36]: 57254 Abort
and this one ...
Code:
Gdk-CRITICAL **: file gdkfont.c: line 220: assertion `font != NULL' failed.
WARNING: core: firefox-bin: PID 57505, failed to write a text area (core file deleted)
moz_run_program[36]: 57505 Memory fault
and the ever-popular
Code:
moz_run_program[36]: 13796 Memory fault
libexc(13937): FATAL ERROR __exc_cache_allocate_node: unable to allocate a new node (128bytes)
WARNING: core: firefox-bin: PID 13937, failed to write a text area (core file deleted)
moz_run_program[36]: 13937 Abort
let's not forget
Code:
fewel 1% atcheckpoint/atrestart failed to mallocNot enough spaceNot enough space
atcheckpoint/atrestart failed to mallocNot enough spaceNot enough space
libexc(1170): FATAL ERROR __exc_add_rld: malloc(36) failed
WARNING: core: firefox-bin: PID 1170, failed to write a text area (core file deleted)
moz_run_program[36]: 1170 Abort
There's a few more but those are the most common ...