ia64/86218: Mozilla / Firefox: regxpcom or regchrome broken on ia64 / FreeBSD-7.

[Thierry Thomas]

>Number:         86218
>Category:       ia64
>Synopsis:       Mozilla / Firefox: regxpcom or regchrome broken on ia64 / FreeBSD-7.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ia64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 16 16:20:11 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Thierry Thomas
>Release:        FreeBSD 6.0-BETA4 i386
>Organization:
Kabbale Eros
>Environment:
System: FreeBSD graf.pompo.net 6.0-BETA4 FreeBSD 6.0-BETA4 #0: Thu Sep 8 19:32:50 CEST 2005 thierry at graf.pompo.net:/usr/obj/usr/src/sys/GRAF050907 i386


	
>Description:
	(Cc: to Mozilla & Firefox maintainers team for information.)

	As reported on pointyhat, several xpi extensions fail because regxpcom
	or regchrome segfault or have an erratic behaviour:

	E.g. adblock-firefox-0.5.d
	<http://pointyhat.freebsd.org/errorlogs/ia64-errorlogs/e.7.2005090702/adblock-firefox-0.5.d.log>
	or bugmenot-0.6.2 or fr-mozilla-flp-1.7.11.

	After installation, these ports rebuild the chrome registry with
	regxpcom and regchrome, two binaries installed by mozilla or firefox
	(see www/mozex/pkg-install.xpi).

>How-To-Repeat:
	Try to install these ports on ia64 / -CURRENT.

>Fix:
	Acording to Marcel Moolenaar, the problem relates to SMP and libpthread.
	In particular the saving and restoring of the high FP registers. If this
	theory is correct, there should be no problems if regxpcom and regchrome
	are linked against libthr.

>Release-Note:
>Audit-Trail:
>Unformatted: