Summary: | www-client/seamonkey-2 Crash 'cause a segmentation default (aparently because of spidermonkey) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Federico Moro <zayer> |
Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | mmokrejs, mozilla |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Federico Moro
2009-11-04 18:41:35 UTC
Try to enable debug following the http://www.gentoo.org/proj/en/qa/backtraces.xml?style=printable guide and preferably also look into bugs #289364 and #289483 and to confirm my findings. You should end up with core dumps generated in /var/dumps/ directory with much more useful backtraces. Do not use -O3, but you can live with "-O2 -ggdb". I cannot reproduce the problem on any of my machines. Are you really sure this is a problem resulting from spidermonkey being installed on your system? Does the error really vanish after you unmerged spidermonkey and re-emerged seamonkey-2? The spidermonkey I've is the one who comes from seamonkey suit, 'cause I can't unmerge spidermonkey without unmerge seamonkey. I'm pretty sure because it crash when I enable javascript. This crash doesn't happend on my ppc32 laptop or using mozilla's seamonkey official binary. I've try everything and still crashing. Well, it seems that anybody cares this bug (like lot of others)... but if somebody cares, I've fix it compiling seamonkey with O2 instead of O3, so you should check it and force seamonkey to don't compile it with O3 if needed. (In reply to comment #4) > Well, it seems that anybody cares this bug (like lot of others)... but if > somebody cares, I've fix it compiling seamonkey with O2 instead of O3, so you > should check it and force seamonkey to don't compile it with O3 if needed. Please report the compilation bug upstream along with the full debug stacktrace. That will ensure upstream fix the source code not to demand too much from the broken compiler. and post here the bug # you have opened at bugzilla.mozilla.org. I can do it for them (mozilla), of course, but until seamonkey-2.0 still crashing because of spidermonkey have been compiled with O3, its ebuild, i.e., should force O2 optimization. This is the only reason I've notice here that it works with O2 on x86 amd athlon-xp as it works with O2 on ppc G4. Does anybody compile seamonkey-2.0 with O3 and it works perfect browsing throw webpages with some javascript? This should actually already be fixed, mozcoreconf-2.eclass now forces --enable-optimize=-O2. If this is not fixed let us know, if it is please mark fixed so it will close. (In reply to comment #7) > This should actually already be fixed, mozcoreconf-2.eclass now forces > --enable-optimize=-O2. If this is not fixed let us know, if it is please mark > fixed so it will close. > Why? Often I need to run: CFLAGS="-O0 -ggdb" emerge seamonkey Any news here? Does this still happen? Please reopen if you still have this problem. |