i'm really having trouble to get a recent enough firefox running on
debian sparc.
I couldn't get firefox to run with the missing libraries taken from
snapshots manually.
Is there any specific snapshot date that is containing working dependencies?If Firefox is installable with the dependencies you pulled without forcing
Also i could not find the sparc64-specific source patches to firefox anywhere.
They are not included in the official patch set.
Hello!
On 7/10/20 11:11 PM, Connor McLaughlan wrote:
i'm really having trouble to get a recent enough firefox running on
debian sparc.
I couldn't get firefox to run with the missing libraries taken from snapshots manually.
That's not enough information to help you debug the problem. I always need
an error message. Normally, a Firefox that managed to build should mostly work fine as the Javascript engine is run during build to transpile some Javascript code.
Is there any specific snapshot date that is containing working dependencies?If Firefox is installable with the dependencies you pulled without forcing dpkg to override dependencies, it should work. If it doesn't, please run Firefox from the command line and provide me with the error message.
Also i could not find the sparc64-specific source patches to firefox anywhere.
They are not included in the official patch set.
There shouldn't be any. I upstreamed all patches.
First i tried to install firefox and it reported the uninstallable dependencies:
root@SunBlade100:/usr/pkgsrc# aptitude install firefox
The following NEW packages will be installed:
firefox{b} libjsoncpp1{a}
0 packages upgraded, 2 newly installed, 0 to remove and 87 not upgraded.
Need to get 34.8 MB of archives. After unpacking 152 MB will be used.
The following packages have unmet dependencies:
firefox : Depends: libevent-2.1-6 (>= 2.1.8-stable) which is a
virtual package and is not provided by any available package
Depends: libffi6 (>= 3.0.4) which is a virtual package and
is not provided by any available package
Depends: libvpx5 (>= 1.6.0) which is a virtual package and
is not provided by any available package
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) firefox [Not Installed]
Then i fetched these dependencies from snapshot, and installed them
together with firefox.
I used these:
https://snapshot.debian.org/archive/debian-ports/20170801T005203Z/pool-sparc64/main/libe/libevent/libevent-2.1-6_2.1.8-stable-4_sparc64.deb
https://snapshot.debian.org/archive/debian-ports/20160224T140706Z/pool-sparc64/main/libf/libffi/libffi6_3.3%7E20160224-1_sparc64.deb
https://snapshot.debian.org/archive/debian-ports/20180217T200112Z/pool-sparc64/main/libv/libvpx/libvpx5_1.7.0-3_sparc64.deb
When i start firefox, i get:
Segmentation fault
You need to install the firefox-dbg package otherwise GDB won't be able to help you.
When i start firefox, i get:
Segmentation fault
gdb tells:
Reading symbols from firefox...
(No debugging symbols found in firefox)
(gdb) run
Starting program: /usr/bin/firefox
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/sparc64-linux-gnu/libthread_db.so.1".
Program received signal SIGILL, Illegal instruction.
0xfffff801068b0754 in ?? () from /lib/sparc64-linux-gnu/libcrypto.so.1.1 (gdb)
Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
MOZ_CrashOOL (aLine=<optimized out>, aReason=0xfffff8010b632bf0 "js::jit::InitProcessExecutableMemory() failed")
at /build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp:33
33 /build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp: No
such file or directory.
(gdb) bt
#0 MOZ_CrashOOL (aLine=<optimized out>,
aReason=0xfffff8010b632bf0 "js::jit::InitProcessExecutableMemory() failed")
at /build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp:33
#1 0xfffff801078134e0 in NS_InitXPCOM2 (aResult=0x700001ea770, aBinDirectory=<optimized out>,
aAppFileLocationProvider=<optimized out>)
at /build/firefox-YyDH69/firefox-62.0.3/xpcom/build/XPCOMInit.cpp:691
#2 0xfffff8010a365638 in ScopedXPCOMStartup::Initialize (this=0x700001ea770)
at /build/firefox-YyDH69/firefox-62.0.3/toolkit/xre/nsXREDirProvider.h:67 #3 0xfffff8010a36dce8 in XREMain::XRE_main (this=0x7feffffdcb8, argc=<optimized out>, argv=<optimized out>,
aConfig=...) at /build/firefox-YyDH69/firefox-62.0.3/toolkit/xre/nsAppRunner.cpp:4888
#4 0xfffff8010a36e1d0 in XRE_main (argc=<optimized out>,
argv=0x7fefffff378, aConfig=...)
at /build/firefox-YyDH69/firefox-62.0.3/toolkit/xre/nsAppRunner.cpp:4984 #5 0x0000010000006210 in do_main (argc=<optimized out>,
argv=0x7fefffff378, envp=0x7fefffff388)
at /build/firefox-YyDH69/firefox-62.0.3/build-browser/dist/include/mozilla/UniquePtr.h:326
#6 0x0000010000005a98 in main (argc=<optimized out>,
argv=0x7fefffff378, envp=0x7fefffff388)
at /build/firefox-YyDH69/firefox-62.0.3/browser/app/nsBrowserApp.cpp:311 (gdb)
/build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp:33
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1441473
On 7/14/20 8:02 PM, Connor McLaughlan wrote:
Thread 1 "firefox" received signal SIGSEGV, Segmentation fault. MOZ_CrashOOL (aLine=<optimized out>, aReason=0xfffff8010b632bf0 "js::jit::InitProcessExecutableMemory() failed")
at /build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp:33
33 /build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp: No
such file or directory.
See, that's the actual crash you were looking for.
(gdb) bt
#0 MOZ_CrashOOL (aLine=<optimized out>,
aReason=0xfffff8010b632bf0 "js::jit::InitProcessExecutableMemory() failed")
at /build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp:33
#1 0xfffff801078134e0 in NS_InitXPCOM2 (aResult=0x700001ea770, aBinDirectory=<optimized out>,
aAppFileLocationProvider=<optimized out>)
at /build/firefox-YyDH69/firefox-62.0.3/xpcom/build/XPCOMInit.cpp:691 #2 0xfffff8010a365638 in ScopedXPCOMStartup::Initialize (this=0x700001ea770)
at /build/firefox-YyDH69/firefox-62.0.3/toolkit/xre/nsXREDirProvider.h:67
#3 0xfffff8010a36dce8 in XREMain::XRE_main (this=0x7feffffdcb8, argc=<optimized out>, argv=<optimized out>,
aConfig=...) at /build/firefox-YyDH69/firefox-62.0.3/toolkit/xre/nsAppRunner.cpp:4888
#4 0xfffff8010a36e1d0 in XRE_main (argc=<optimized out>, argv=0x7fefffff378, aConfig=...)
at /build/firefox-YyDH69/firefox-62.0.3/toolkit/xre/nsAppRunner.cpp:4984
#5 0x0000010000006210 in do_main (argc=<optimized out>, argv=0x7fefffff378, envp=0x7fefffff388)
at /build/firefox-YyDH69/firefox-62.0.3/build-browser/dist/include/mozilla/UniquePtr.h:326
#6 0x0000010000005a98 in main (argc=<optimized out>,
argv=0x7fefffff378, envp=0x7fefffff388)
at /build/firefox-YyDH69/firefox-62.0.3/browser/app/nsBrowserApp.cpp:311
(gdb)
So, this is an intentional crash here:
/build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp:33
which is triggered by the function "js::jit::InitProcessExecutableMemory()" failing.
The Javascript memory management in Firefox can be nasty when running on an architecture
with virtual address spaces larger than 47 bits [1]. I suggest using an earlier Firefox
version (like 60).
It might also be an unrelated bug for which NetBSD is carrying a fix.
Adrian
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1441473
On 7/14/20 10:43 PM, Connor McLaughlan wrote:
That is the problem: i am unable to locate any working version.
I would even use a firefox-52 or something if it was available.
On the repository there are:
firefox 62.0.3-1
firefox-esr 60.8.0esr-1
Both are segfaulting.
I searched snaphot the whole evening for available versions.
I could not find any sparc64 version of firefox 52.
The earliest i could find is firefox-esr 60.1.0esr-3, which is also segfaulting.
Any hints for any working firefox versions on debian sparc64 are welcome.
I know that 60 or so was working, because I was using it myself.
Adrian
On 7/14/20 11:47 PM, Connor McLaughlan wrote:
I have also tried these version now - all segfaulting:
firefox_59.0~b4-1_sparc64.deb
firefox-esr_60.2.0esr-1_sparc64.deb
firefox-esr_60.8.0esr-1_sparc64.deb
I know that the latest firefox working on netbsd sparc64 is 52, so i
wonder if this is different for linux?
Unfortunately it seems during the time firefox 52 was available on
debian, there were no builds made for sparc64.
Is someone still browsing the web with their sparc boxes on a recent debian? If so, what browser are you using?
Have you verified the RAM in the machine is working fine?
As I said before, the JavaScript engine is invoked during build
that indicates that its generally working.
If it's not hardware-related, it's an issue in another package.
On 7/17/20 4:00 PM, Connor McLaughlan wrote:
If it's not hardware-related, it's an issue in another package.
I doubt that it is a hardware failure. Firefox also segfaults on qemu-sparc64.
Also firefox52 on netbsd is working on this machine, but of course you can't compare this.
And i couldn't find firefox52 for debian sparc64.
http://snapshot.debian.org/archive/debian-ports/20161230T183525Z/pool-sparc64/main/f/firefox/firefox_50.1.0-1_sparc64.deb
http://snapshot.debian.org/archive/debian-ports/20180131T201111Z/pool-sparc64/main/f/firefox/firefox_59.0%7Eb4-1_sparc64.deb
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 66:25:59 |
| Calls: | 6,654 |
| Files: | 12,200 |
| Messages: | 5,331,881 |