Hi Adrian,
I’m getting stuck building firefox, and as you’re building it already, how do
we get past this?
thanks,
Ken
I did this:
$ apt-get build-dep firefox
$ apt source firefox
$ apt install python-is-python3
$ cd firefox-120.0
$ dpkg-buildpackage -us -uc
but I keep getting this:
——
Hi!
On Thu, 2023-11-23 at 23:45 +0100, kristoffer...@tuta.io wrote:
>
> Deeper debugging is beyond my skills. I don't know if this helps but the "bt"
> command gave me this:
>
> (gdb) bt
> #0 i32_load8_u (addr=2016478208, mem=) at rlbox.wasm.c:146
> #1 w2c_rlbox_streqci
Deeper debugging is beyond my skills. I don't know if this helps but the "bt"
command gave me this:
(gdb) bt
#0 i32_load8_u (addr=2016478208, mem=) at rlbox.wasm.c:146
#1 w2c_rlbox_streqci (var_p0=var_p0@entry=262000, var_p1=2016478208,
instance=) at rlbox.wasm.c:1499
#2 0x7fffe91969a8 in
Am Donnerstag, dem 23.11.2023 um 09:01 +0100 schrieb Johannes
Brakensiek:
> Crashdump was attached.
Backtrace, to be more precise.
Johannes
Hi,
Am Mittwoch, dem 22.11.2023 um 10:18 +0100 schrieb
kristoffer...@tuta.io:
> I caught this today thru gdb and Firefox 120.0-1 on my dual G5:
>
> Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
> i32_load8_u (addr=2016478208, mem=) at
> rlbox.wasm.c:146
> 146 rlbox.wasm.c: No
Hi,
I caught this today thru gdb and Firefox 120.0-1 on my dual G5:
Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
i32_load8_u (addr=2016478208, mem=) at rlbox.wasm.c:146
146 rlbox.wasm.c: No such file or directory.
Regards,
Kris
--
Wysyłano z Tuta, ciesz się bezpiecznymi
Hi!
On Tue, 2023-11-21 at 22:05 +0100, Johannes Brakensiek wrote:
> Am Dienstag, dem 21.11.2023 um 21:20 +0100 schrieb John Paul Adrian
> Glaubitz:
> >
> > Please test this build which include the image decoder big-endian fix
> > from VoidPPC:
> >
> > >
Hi Adrian,
Am Dienstag, dem 21.11.2023 um 21:20 +0100 schrieb John Paul Adrian
Glaubitz:
>
> Please test this build which include the image decoder big-endian fix
> from VoidPPC:
>
> > https://people.debian.org/~glaubitz/firefox-ppc64/test002/
>
> Adrian
>
thanks for providing the binary. It
On Tue, 2023-11-21 at 20:38 +0100, John Paul Adrian Glaubitz wrote:
> I have just been reminded by a comment in the upstream bug report [1] that
> the VoidPPC
> project actually has a number of patches which fix issues in Firefox on
> PowerPC [2] and
> I'm rebuilding Firefox with this patch [3]
Hi!
On Mon, 2023-11-20 at 22:32 +0100, John Paul Adrian Glaubitz wrote:
> There is currently no up-to-date version of Firefox for 32-bit PowerPC since
> Firefox
> currently requires NodeJS to build which is not available on 32-bit PowerPC
> at the
> moment.
>
> It is actually possible,
On Tue, 2023-11-21 at 08:32 -0800, Ken Cunningham wrote:
> I added an 8GB swapfile, and (slowly) got this backtrace:
>
> # cat error.txt
> Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
> i32_load8_u (addr=2014643200, mem=) at rlbox.wasm.c:146
> 146 rlbox.wasm.c: No such file
I added an 8GB swapfile, and (slowly) got this backtrace:
# cat error.txt
Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
i32_load8_u (addr=2014643200, mem=) at rlbox.wasm.c:146
146 rlbox.wasm.c: No such file or directory.
(gdb) bt
#0 i32_load8_u (addr=2014643200, mem=) at
Trying to run firefox under gdb with the debug symbols installed appears to
result in an out-of-memory situation on my DualG5 with 3.5GB ram, I’m afraid.
Perhaps someone else has a system with more memory, or set up better than mine,
that could help.
Ken
-
$ gdb firefox
GNU gdb (Debian
To be honest, I did run it under gdb, and ran the backtrace, but the backtrace
was mostly uninterpretable without the debug symbols of course.
So somewhere in libxul was all I could offer.
I’ll see if adding the debug symbols narrows it down a bit.
Ken
> On Nov 21, 2023, at 02:13, John Paul
Hello!
On Mon, 2023-11-20 at 15:39 -0800, Ken Cunningham wrote:
> on my system I had another segfault, in libxul.
A more detailed backtrace would be useful. libxul is basically all of
Firefox, so referring to a crash in libxul is not saying much.
Try installing the debug package from here:
>
> On Nov 20, 2023, at 12:37 PM, Jeffrey Walton wrote:
>
> On Mon, Nov 20, 2023 at 1:56 PM Ken Cunningham
> wrote:
>>
>> On 2023-11-20, at 2:06 AM, John Paul Adrian Glaubitz wrote:
>>
On Nov 20, 2023, at 10:56 AM, Jeroen Diederen
wrote:
Firefox does not work.
>>>
>>>
On 2023-11-20, at 3:21 PM, John Paul Adrian Glaubitz wrote:
> On Mon, 2023-11-20 at 22:32 +0100, John Paul Adrian Glaubitz wrote:
>> Anyways, this particular crash a known upstream bug in Firefox [2]. I wonder
>> whether
>> it might be fixed by this particular patch [3].
>
> I have rebuild
On Mon, 2023-11-20 at 22:32 +0100, John Paul Adrian Glaubitz wrote:
> Anyways, this particular crash a known upstream bug in Firefox [2]. I wonder
> whether
> it might be fixed by this particular patch [3].
I have rebuild the Firefox package for ppc64 with this patch included:
>
Hi Jeffrey!
On Mon, 2023-11-20 at 15:37 -0500, Jeffrey Walton wrote:
> On Mon, Nov 20, 2023 at 1:56 PM Ken Cunningham
> wrote:
> >
> >
> > The one I have installed is:
> >
> > firefox/unstable,now 119.0.1-1 ppc64
> >
> > and it has a segmentation fault when you launch it.
>
> Out of
On Mon, Nov 20, 2023 at 1:56 PM Ken Cunningham
wrote:
>
> On 2023-11-20, at 2:06 AM, John Paul Adrian Glaubitz wrote:
>
> >> On Nov 20, 2023, at 10:56 AM, Jeroen Diederen
> >> wrote:
> >>
> >> Firefox does not work.
> >
> > Did you try the latest version 119?
> >
> > If there is a patch which
On 2023-11-20, at 2:06 AM, John Paul Adrian Glaubitz wrote:
> Hello!
>
>> On Nov 20, 2023, at 10:56 AM, Jeroen Diederen wrote:
>>
>> Firefox does not work.
>
> Did you try the latest version 119?
>
> If there is a patch which fixes the crash on big-endian targets, we could
> include it in
Hello!
> On Nov 20, 2023, at 10:56 AM, Jeroen Diederen wrote:
>
> Firefox does not work.
Did you try the latest version 119?
If there is a patch which fixes the crash on big-endian targets, we could
include it in the Debian package or I could try to get it merged upstream.
Adrian
Hi Adrian,
Firefox does not work.
Regards,
Jeroen
John Paul Adrian Glaubitz schreef op 2023-11-20 13:01:
On Sun, 2023-11-19 at 16:46 -0800, Ken Cunningham wrote:
Does anyone have or know about a browser they use on debian
ppc64 they would feel comfortable to recommend?
Firefox is available
Hi Ken,
Ken Cunningham wrote:
> I am aware of a few projects out there working to try to keep a repackaged
> TenFourFox going that have *.deb archives available, and I think there are
> some official channels for a few different browsers inside debian (Firefox,
> Epiphany).
I don't know what
On Sun, 2023-11-19 at 16:46 -0800, Ken Cunningham wrote:
> Does anyone have or know about a browser they use on debian
> ppc64 they would feel comfortable to recommend?
Firefox is available and up to date for ppc64.
> https://buildd.debian.org/status/package.php?p=firefox=sid
Did you try to
Yes, that one works pretty well, better than I expected it would.
Thank you!
To get it to launch, I had to make a symlink, as it’s built against libffi6 but
that version is not available any more on any of my apt sources it appears.…
ie in:
/usr/lib/powerpc64-linux-gnu
I did this, which
SeaLion (https://github.com/wicknix/SeaLion) is the best choice for
PowerPC.
On Sun, Nov 19, 2023 at 7:46 PM Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:
> I am aware of a few projects out there working to try to keep a repackaged
> TenFourFox going that have *.deb archives
27 matches
Mail list logo
