Bug#775321: x32 port

Adam Borowski kilobyte at angband.pl
Tue Jan 20 03:51:05 UTC 2015


On Wed, Jan 14, 2015 at 01:33:18PM +0900, Mike Hommey wrote:
> That means the xpcshell is broken in some way which means iceweasel is
> likely to be broken as well.

xpcshell passed both whatever tests are done during the build, and my sanity
checks, yet it fails on xpconnect.  Iceweasel gives more useful data when
ran under gdb:

Program received signal SIGSEGV, Segmentation fault.
0xce572460 in ?? ()
(gdb) bt
#0  0xce572460 in ?? ()
#1  0xf2f57de0 in NS_InvokeByIndex (that=<optimized out>, methodIndex=<optimized out>, 
    paramCount=<optimized out>, params=<optimized out>)
    at /home/kilobyte/tmp/x32/iceweasel-35.0/xpcom/reflect/xptcall/md/unix/xptcinvoke_x86_64_unix.cpp:164
#2  0xf329fe91 in Invoke (this=0xffffa848)
    at /home/kilobyte/tmp/x32/iceweasel-35.0/js/xpconnect/src/XPCWrappedNative.cpp:2396
[...]

So it turns out the xptcall part requires specific support for every
architecture.  I'm afraid I can't port this part myself (the last time I
did serious assembler was 8086...).  I wonder who could help...


> Or that you can't run x32 binaries on your build host.

I'm porting this (and everything else) natively.  Mostly in a chroot, as for
proper dogfooding one would want, you know, a proper browser...


Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable and Non-Discriminatory prices.



More information about the pkg-mozilla-maintainers mailing list