Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-15 Thread Lennart Sorensen 
On Mon, Feb 13, 2017 at 04:44:22PM -0500,  wrote:
> Well there does exist cheaper options, like the $4k T4240QDS-PB, which
> is 12 core (24 threads) 1.8Ghz 64 bit powerpc.
> 
> The P5040RDB is $3k for a quad core 64 bit powerpc.
> 
> That's still not hobby level pricing though.  Better than the price of
> the talos, but also not ppc64el compatible (as far as I know).

Seems you can get an IBM S812LC with an 8 core Power8 for under $5k with
32GB ram.  That would make for a nice build machine.  You wouldn't want
to be anywhere near it due to the fan noise though.

-- 
Len Sorensen

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread luigi burdo 
P5040 is much less then 3k in prize or there is P5020 too *cyrus plus

or the old good G5 Quad.. it rulez today im writing right now from fedora 25 
PPC64 firefox 51 and i dont miss a new gen machine. Work in full PPC64 made 
this machine really enjoyable.


Luigi



Da: Lennart Sorensen 
Inviato: lunedì 13 febbraio 2017 22.44
A: Konstantinos Margaritis
Cc: debian-powerpc@lists.debian.org
Oggetto: Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): 
Segmentation fault

On Mon, Feb 13, 2017 at 10:44:57PM +0200, Konstantinos Margaritis wrote:
> As with all new languages it will take time, but eventually it will get
> there, with a big IF. The biggest(only?) problem with PowerPC in
> general right now is hardware availability not lack of interested
> developers. Developers will try anything new if it's decently priced
> (as ARM/MIPS have already proven). Show me a decent 64-bit PowerPC
> board at ~100-200EUR, Talos was a great idea, but about $17k more
> expensive than it should have been.

Well there does exist cheaper options, like the $4k T4240QDS-PB, which
is 12 core (24 threads) 1.8Ghz 64 bit powerpc.

The P5040RDB is $3k for a quad core 64 bit powerpc.

That's still not hobby level pricing though.  Better than the price of
the talos, but also not ppc64el compatible (as far as I know).

--
Len Sorensen

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread Lennart Sorensen 
On Mon, Feb 13, 2017 at 10:44:57PM +0200, Konstantinos Margaritis wrote:
> As with all new languages it will take time, but eventually it will get
> there, with a big IF. The biggest(only?) problem with PowerPC in
> general right now is hardware availability not lack of interested
> developers. Developers will try anything new if it's decently priced
> (as ARM/MIPS have already proven). Show me a decent 64-bit PowerPC
> board at ~100-200EUR, Talos was a great idea, but about $17k more
> expensive than it should have been.

Well there does exist cheaper options, like the $4k T4240QDS-PB, which
is 12 core (24 threads) 1.8Ghz 64 bit powerpc.

The P5040RDB is $3k for a quad core 64 bit powerpc.

That's still not hobby level pricing though.  Better than the price of
the talos, but also not ppc64el compatible (as far as I know).

-- 
Len Sorensen

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread John Paul Adrian Glaubitz 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/13/2017 09:44 PM, Konstantinos Margaritis wrote:
> I'm not a compiler developer, but I've done my share of compiler 
> bootstrapping/bug reporting/bug fixing.

Same here. I'm just more involved with gcc on targets like SH, sparc64
and m68k.

> In fact I'm one of the maintainers of LDC (LLVM D compiler), and I've 
> bootstrapped the package for armhf/ppc64/ppc64le and working on arm64/powerpc 
> and
> other arches to follow (s390x/mips*) when I have the time. I've also done 
> quite a few bug reports to gcc upstream (mostly NEON ICEs for armhf). So I 
> have a
> pretty good idea of what's involved, though I've only scratched Rust on the 
> surface and never actually developed on/for it.

Ok. It first sound like you thought it would be a trivial thing to do.
- From my experience, getting compilers work properly can be quite involved
on non-mainstream architectures. People are normally used to compilers
to be nearly bug free from their experience on x86 targets but that's
often not the case on other architectures. On SH, for example, there
were over 20 bugs to be fixed until the SH backend for gcc-5 was properly
working.

> I know for a fact that there are people pushing for IBM to actively support 
> Rust on ppc64*. Whether that works or not, I have no idea, but at least people
> are not idle.

I have heard the same, yes. But the question is whether this is endorsed
by IBM themselves or just some people working at IBM. Unlike Golang, Rust
doesn't have a big usecase which makes it attractive for porters. For Golang,
it's container technology and all the projects around it. Nearly every company
wants to jump the container hypetrain and that's why Golang is coming to
more and more platforms. Plus, Go has a second implementation called
gccgo which reaches even more targets.

> As with all new languages it will take time, but eventually it will get 
> there, with a big IF. The biggest(only?) problem with PowerPC in general 
> right now
> is hardware availability not lack of interested developers. Developers will 
> try anything new if it's decently priced (as ARM/MIPS have already proven).
> Show me a decent 64-bit PowerPC board at ~100-200EUR, Talos was a great idea, 
> but about $17k more expensive than it should have been.

The problem with Rust is that there isn't even a stable and fully
supported ARM port despite ARM being one of the largest targets
Linux runs on. x86 is their only tier 1 architecture, the rest
is tier 2 or lower.

If Mozilla wants Rust to be a serious competitor to C++, they will
have to stack up their resources but I doubt they have the finanical
power to do that. They're not Google and their contract with Yahoo
will probably not be extended either now that Yahoo has been bought
by Verizon.

Adrian

- -- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAliiHisACgkQdCY7N/W1
+RP+zA//Sfdeeq7hF9Pc3OQiqo1ItYhp0R72Qhj/62roGpCiLjqh6FktfwNNmhTN
GcMwE7rvkzpLDS6fAlmjx8RANqH6qmFug4rmg6XFYM2NGTe/wjWoxrHOFiGpaPpd
u2Sd2FG0pDBHbw/LRV93FF95TPEA23EpbejQqkva68KdrWQ7qgA2YUdZ+W0Opyf9
y43unP6nCDWrZZAdIOeOml/H0G8yf7RdJ4l2NBZZAAu5huMlUInrGE/ZmdoDlLQI
wy74b2XBVFlGc+Z6REY38XrG77ZhHuv66zw3TPD6PElXMGnETDfYtq0QdrVv5dX6
iHk60cM4cbK0pYxEP/ylaxkeugYHy3fw7o0OyvE/eQOUwoxF2xrlKd5wrL4MznQF
TuTq5hwGB8cJ276oBJFbp1kvk3JUkz+z5dVQGbomjtitT1UDTi8LsnJs+5UQTeOc
Gn0u+6vk1+HPp4Tv//0rSC4X8wOYzuwwH9ri2aWg+5vBpn7BCykRCfiZDZ9/EE9C
lMNl3JBb7MwLmM6Bvn4SOxg9VgSOhRma6GpcIPlYQx9VWYtFP6LZgRovGB/RY115
A/rYOa00LVEObQRLBntWKlLbd1wgPb6E8KNo+1QVuhKeW91fmz8QOgIsfCZQ3Iwd
CWiXBoy/AZV3T9D8X2QUPjYTNkD9VpuwWyqnHrfcME81oBLxTB4=
=4HVI
-END PGP SIGNATURE-

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread Konstantinos Margaritis 
Στις 13-02-2017, ημέρα Δευ, και ώρα 21:00 +0100, ο/η John Paul Adrian
Glaubitz έγραψε:
> I don't know whether you have already dealt with the internals of
> compilers in the past, but I can tell you that it isn't a matter of
> just "fixing" it. For it to work, someone actually has to maintain
> the codebase for this target. Because as the code is being developed,
> it will break again and again unless someone actually tests the code
> on these architectures.

I'm not a compiler developer, but I've done my share of compiler
bootstrapping/bug reporting/bug fixing. In fact I'm one of the
maintainers of LDC (LLVM D compiler), and I've bootstrapped the package
for armhf/ppc64/ppc64le and working on arm64/powerpc and other arches
to follow (s390x/mips*) when I have the time. I've also done quite a
few bug reports to gcc upstream (mostly NEON ICEs for armhf). So I have
a pretty good idea of what's involved, though I've only scratched Rust
on the surface and never actually developed on/for it.

> The problem is that - unlike Golang - no one outside Mozilla cares
> seriously
> enough about Rust that they would maintain it on other architectures.
> For
> Google's Golang, the architecture ports are maintained by the
> hardware
> vendors themselves. For example, IBM maintains Golang on POWER
> (ppc64el
> and ppc64 and zSeries, Google (being a big ARM supporter because of
> Android)
> themselves maintain Golang on ARM, Oracle on sparc64 and so on.

I know for a fact that there are people pushing for IBM to actively
support Rust on ppc64*. Whether that works or not, I have no idea, but
at least people are not idle.

> For Rust, there is currently no such support. Mozilla develops and
> tests
> on x86 only. Everything else is not guaranteed to work at all and may
> blow up in your face.

As with all new languages it will take time, but eventually it will get
there, with a big IF. The biggest(only?) problem with PowerPC in
general right now is hardware availability not lack of interested
developers. Developers will try anything new if it's decently priced
(as ARM/MIPS have already proven). Show me a decent 64-bit PowerPC
board at ~100-200EUR, Talos was a great idea, but about $17k more
expensive than it should have been.

Regards

Konstantinos

signature.asc
Description: This is a digitally signed message part

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread John Paul Adrian Glaubitz 
On 02/13/2017 08:26 PM, Konstantinos Margaritis wrote:
>> Yes. Everyone who is basing their work on Firefox will have to move
>> to a different
>> codebase from version 53 on or fork Firefox and continue without
>> Rust.
> 
> Or, fix Rust for powerpc?

I don't know whether you have already dealt with the internals of
compilers in the past, but I can tell you that it isn't a matter of
just "fixing" it. For it to work, someone actually has to maintain
the codebase for this target. Because as the code is being developed,
it will break again and again unless someone actually tests the code
on these architectures.

The problem is that - unlike Golang - no one outside Mozilla cares seriously
enough about Rust that they would maintain it on other architectures. For
Google's Golang, the architecture ports are maintained by the hardware
vendors themselves. For example, IBM maintains Golang on POWER (ppc64el
and ppc64 and zSeries, Google (being a big ARM supporter because of Android)
themselves maintain Golang on ARM, Oracle on sparc64 and so on.

For Rust, there is currently no such support. Mozilla develops and tests
on x86 only. Everything else is not guaranteed to work at all and may
blow up in your face.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread Konstantinos Margaritis 
Στις 13-02-2017, ημέρα Δευ, και ώρα 20:20 +0100, ο/η John Paul Adrian
Glaubitz έγραψε:
> Yes. Everyone who is basing their work on Firefox will have to move
> to a different
> codebase from version 53 on or fork Firefox and continue without
> Rust.

Or, fix Rust for powerpc?

My 2c.

Konstantinos

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread John Paul Adrian Glaubitz 
On 02/13/2017 01:25 PM, Herminio Hernandez, Jr. wrote:
> This does not surprise me. It is a really sad case. Even the developer of the
> TenFourFox port of FF knows that he will have to cease being code compatible.

Yes. Everyone who is basing their work on Firefox will have to move to a 
different
codebase from version 53 on or fork Firefox and continue without Rust.

> Right now I am using Midori, but once that moves to webkit2gtk life will be 
> painful.

I think Webkit is still portable to all architectures and not limited to x86.

> Here is backtrace I did.

This is actually a useful backtrace. And it's most likely this bug [1].

Adrian

> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1269654

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread Herminio Hernandez, Jr. 
This does not surprise me. It is a really sad case. Even the developer of
the TenFourFox port of FF knows that he will have to cease being code
compatible. Right now I am using Midori, but once that moves to webkit2gtk
life will be painful.

Here is backtrace I did.

On Mon, Feb 13, 2017 at 4:26 AM, luigi burdo 
wrote:

> It means all are killing us in all fronts.
>
> [image: ☹]
>
>
> Luigi
>
>
> --
> *Da:* John Paul Adrian Glaubitz 
> *Inviato:* lunedì 13 febbraio 2017 11.49
> *A:* debian-powerpc@lists.debian.org
> *Oggetto:* Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC
> (PPC32): Segmentation fault
>
> Hi!
>
> On 02/06/2017 10:39 PM, Christian Zigotzky wrote:
> > I installed Firefox 51.0.1-1 with 'apt-get install -t experimental
> firefox'
> > on Debian Sid/experimental PowerPC (PPC32) today.
>
> Just as a warning in advance: Mozilla upstream has decided to make the Rust
> programming language mandatory for Firefox 54 onwards [1].
>
> Unfortunately, Mozilla currently has little interest to support Rust
> non-x86
> platforms in a stable manner which is why the Rust compiler rustc is
> currently
> really usable on i386, amd64 and with some luck on arm64 [2].
>
> Thus, it can be expected that Firefox 54 and newer will no longer run on
> any PowerPC platforms, especially 32-bit variants.
>
> It's a sad state but Mozilla upstream has decided to make this cut which
> will also eventually see the removal of XUL support and hence the support
> for most of the popular Addons that exist in Firefox like Vimperator.
>
> Adrian
>
> > [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1284816
> 1284816 – Require Rust to build - bugzilla.mozilla.org
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1284816>
> bugzilla.mozilla.org
> At some point we're going to require Rust to build Firefox. This is a
> blocker to writing any critical components in Rust. Once we've fixed the
> blockers of bug 1283898 ...
>
>
> > [2] http://lists.alioth.debian.org/pipermail/pkg-rust-
> maintainers/Week-of-Mon-20161226/000758.html
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>
>
rican-linux@debian-ppc:~$ gdb firefox.real
]GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from firefox.real...Reading symbols from /usr/lib/debug/.build-id/a6/81b7e65ae15687f43f84f7c55dfc4626f13bda.debug...done.
done.
(gdb) run http://mozilla.org
Starting program: /usr/bin/firefox.real http://mozilla.org
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
[New Thread 0xb79ff450 (LWP 2332)]
[New Thread 0xb5c3a450 (LWP 2333)]
[Thread 0xb5c3a450 (LWP 2333) exited]
[New Thread 0xb5c3a450 (LWP 2335)]
[New Thread 0xb49ca450 (LWP 2336)]
[New Thread 0xb3fff450 (LWP 2337)]
[New Thread 0xb37ff450 (LWP 2338)]
[New Thread 0xb2fff450 (LWP 2339)]
[New Thread 0xb27ff450 (LWP 2340)]
[New Thread 0xb1fff450 (LWP 2341)]
[New Thread 0xb17ff450 (LWP 2342)]
[New Thread 0xb0bff450 (LWP 2343)]
[New Thread 0xb03ff450 (LWP 2344)]
[New Thread 0xafb09450 (LWP 2345)]
[New Thread 0xaf309450 (LWP 2346)]
[New Thread 0xb7f8a450 (LWP 2348)]
[New Thread 0xae5ff450 (LWP 2349)]
[New Thread 0xad6ff450 (LWP 2350)]
[New Thread 0xac7ff450 (LWP 2351)]
[Thread 0xac7ff450 (LWP 2351) exited]
[New Thread 0xac7ff450 (LWP 2352)]
[New Thread 0xabd0b450 (LWP 2353)]
[New Thread 0xab50b450 (LWP 2354)]
[Thread 0xac7ff450 (LWP 2352) exited]
[New Thread 0xac7ff450 (LWP 2356)]
[New Thread 0xaae85450 (LWP 2357)]
[New Thread 0xa9fff450 (LWP 2358)]
[New Thread 0xa97ff450 (LWP 2359)]
[New Thread 0xa8fff450 (LWP 2360)]
[New Thread 0xa87ff450 (LWP 2361)]
[New Thread 0xa7bff450 (LWP 2362)]
[New Thread 0xa73ff450 (LWP 2363)]
[New Thread 0xa6bff450 (LWP 2364)]
[New Thread 0xa63ff450 (LWP 2365)]
[Thread 0xa63ff450 (LWP 2

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread luigi burdo 
It means all are killing us in all fronts.

[☹]


Luigi



Da: John Paul Adrian Glaubitz 
Inviato: lunedì 13 febbraio 2017 11.49
A: debian-powerpc@lists.debian.org
Oggetto: Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): 
Segmentation fault

Hi!

On 02/06/2017 10:39 PM, Christian Zigotzky wrote:
> I installed Firefox 51.0.1-1 with 'apt-get install -t experimental firefox'
> on Debian Sid/experimental PowerPC (PPC32) today.

Just as a warning in advance: Mozilla upstream has decided to make the Rust
programming language mandatory for Firefox 54 onwards [1].

Unfortunately, Mozilla currently has little interest to support Rust non-x86
platforms in a stable manner which is why the Rust compiler rustc is currently
really usable on i386, amd64 and with some luck on arm64 [2].

Thus, it can be expected that Firefox 54 and newer will no longer run on
any PowerPC platforms, especially 32-bit variants.

It's a sad state but Mozilla upstream has decided to make this cut which
will also eventually see the removal of XUL support and hence the support
for most of the popular Addons that exist in Firefox like Vimperator.

Adrian

> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1284816
1284816 – Require Rust to build - 
bugzilla.mozilla.org<https://bugzilla.mozilla.org/show_bug.cgi?id=1284816>
bugzilla.mozilla.org
At some point we're going to require Rust to build Firefox. This is a blocker 
to writing any critical components in Rust. Once we've fixed the blockers of 
bug 1283898 ...



> [2] 
> http://lists.alioth.debian.org/pipermail/pkg-rust-maintainers/Week-of-Mon-20161226/000758.html

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-13 Thread John Paul Adrian Glaubitz 
Hi!

On 02/06/2017 10:39 PM, Christian Zigotzky wrote:
> I installed Firefox 51.0.1-1 with 'apt-get install -t experimental firefox'
> on Debian Sid/experimental PowerPC (PPC32) today.

Just as a warning in advance: Mozilla upstream has decided to make the Rust
programming language mandatory for Firefox 54 onwards [1].

Unfortunately, Mozilla currently has little interest to support Rust non-x86
platforms in a stable manner which is why the Rust compiler rustc is currently
really usable on i386, amd64 and with some luck on arm64 [2].

Thus, it can be expected that Firefox 54 and newer will no longer run on
any PowerPC platforms, especially 32-bit variants.

It's a sad state but Mozilla upstream has decided to make this cut which
will also eventually see the removal of XUL support and hence the support
for most of the popular Addons that exist in Firefox like Vimperator.

Adrian

> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1284816
> [2] 
> http://lists.alioth.debian.org/pipermail/pkg-rust-maintainers/Week-of-Mon-20161226/000758.html

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-12 Thread Herminio Hernandez Jr. 
Running debug now with the symbols. 

Sent from my iPhone

> On Feb 12, 2017, at 8:50 AM, Christian Zigotzky  
> wrote:
> 
> Hi Herminio,
> 
> If you want to backtrace Firefox, then you need the debug version of Firefox. 
> Please add the following repositories to your /etc/apt/sources.list:
> 
> deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main
> deb http://debug.mirrors.debian.org/debian-debug/ experimental-debug main
> 
> You have to install the Firefox package with dbgsym attached:
> 
> apt-get install -t experimental firefox-dbgsym
> 
> Many thanks for your help.
> 
> Cheers,
> Christian
> 
>> On 12 February 2017 at 10:18 AM, John Paul Adrian Glaubitz wrote:
>>> On 02/12/2017 08:37 AM, Herminio Hernandez, Jr. wrote:
>>> I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace. 
>>> I am posting it here.
>> This backtrace is not usable, it doesn't contains any symbols:
>> 
>> Thread 1 "firefox.real" received signal SIGSEGV, Segmentation fault.
>> 0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
>> (gdb) bt
>> #0  0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
>> #1  0x1ae2eed4 in ?? () from /usr/lib/firefox/libxul.so
>> #2  0x20017584 in ?? ()
>> (...)
>> 
>> The "??" indicates you don't have debug symbols installed.
>> 
>> Adrian
>> 
>

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-12 Thread Herminio Hernandez Jr. 
Will do. Anything to help. 

Sent from my iPhone

> On Feb 12, 2017, at 8:50 AM, Christian Zigotzky  
> wrote:
> 
> Hi Herminio,
> 
> If you want to backtrace Firefox, then you need the debug version of Firefox. 
> Please add the following repositories to your /etc/apt/sources.list:
> 
> deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main
> deb http://debug.mirrors.debian.org/debian-debug/ experimental-debug main
> 
> You have to install the Firefox package with dbgsym attached:
> 
> apt-get install -t experimental firefox-dbgsym
> 
> Many thanks for your help.
> 
> Cheers,
> Christian
> 
>> On 12 February 2017 at 10:18 AM, John Paul Adrian Glaubitz wrote:
>>> On 02/12/2017 08:37 AM, Herminio Hernandez, Jr. wrote:
>>> I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace. 
>>> I am posting it here.
>> This backtrace is not usable, it doesn't contains any symbols:
>> 
>> Thread 1 "firefox.real" received signal SIGSEGV, Segmentation fault.
>> 0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
>> (gdb) bt
>> #0  0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
>> #1  0x1ae2eed4 in ?? () from /usr/lib/firefox/libxul.so
>> #2  0x20017584 in ?? ()
>> (...)
>> 
>> The "??" indicates you don't have debug symbols installed.
>> 
>> Adrian
>> 
>

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-12 Thread Christian Zigotzky 

Hi Herminio,

If you want to backtrace Firefox, then you need the debug version of 
Firefox. Please add the following repositories to your 
/etc/apt/sources.list:


deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main
deb http://debug.mirrors.debian.org/debian-debug/ experimental-debug main

You have to install the Firefox package with dbgsym attached:

apt-get install -t experimental firefox-dbgsym

Many thanks for your help.

Cheers,
Christian

On 12 February 2017 at 10:18 AM, John Paul Adrian Glaubitz wrote:

On 02/12/2017 08:37 AM, Herminio Hernandez, Jr. wrote:

I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace. I 
am posting it here.

This backtrace is not usable, it doesn't contains any symbols:

Thread 1 "firefox.real" received signal SIGSEGV, Segmentation fault.
0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
(gdb) bt
#0  0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
#1  0x1ae2eed4 in ?? () from /usr/lib/firefox/libxul.so
#2  0x20017584 in ?? ()
(...)

The "??" indicates you don't have debug symbols installed.

Adrian

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-12 Thread Herminio Hernandez Jr. 
You are right. I will install them and run again. 

Sent from my iPhone

> On Feb 12, 2017, at 2:18 AM, John Paul Adrian Glaubitz 
>  wrote:
> 
>> On 02/12/2017 08:37 AM, Herminio Hernandez, Jr. wrote:
>> I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace. 
>> I am posting it here.
> 
> This backtrace is not usable, it doesn't contains any symbols:
> 
> Thread 1 "firefox.real" received signal SIGSEGV, Segmentation fault.
> 0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
> (gdb) bt
> #0  0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
> #1  0x1ae2eed4 in ?? () from /usr/lib/firefox/libxul.so
> #2  0x20017584 in ?? ()
> (...)
> 
> The "??" indicates you don't have debug symbols installed.
> 
> Adrian
> 
> -- 
> .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-12 Thread luigi burdo 
the strange it is working  without issue if i dont count the strange webm 
0x0x24 resolution in video (no video) on fedora and ubuntu mate 16.10.
and on mate i was using the debian sid build.

luigi
Inviato da iPad

> Il giorno 12 feb 2017, alle ore 10:19, John Paul Adrian Glaubitz 
>  ha scritto:
> 
>> On 02/12/2017 08:37 AM, Herminio Hernandez, Jr. wrote:
>> I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace. 
>> I am posting it here.
> 
> This backtrace is not usable, it doesn't contains any symbols:
> 
> Thread 1 "firefox.real" received signal SIGSEGV, Segmentation fault.
> 0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
> (gdb) bt
> #0  0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
> #1  0x1ae2eed4 in ?? () from /usr/lib/firefox/libxul.so
> #2  0x20017584 in ?? ()
> (...)
> 
> The "??" indicates you don't have debug symbols installed.
> 
> Adrian
> 
> -- 
> .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-12 Thread John Paul Adrian Glaubitz 
On 02/12/2017 08:37 AM, Herminio Hernandez, Jr. wrote:
> I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace. I 
> am posting it here.

This backtrace is not usable, it doesn't contains any symbols:

Thread 1 "firefox.real" received signal SIGSEGV, Segmentation fault.
0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
(gdb) bt
#0  0x1ae2ddf8 in ?? () from /usr/lib/firefox/libxul.so
#1  0x1ae2eed4 in ?? () from /usr/lib/firefox/libxul.so
#2  0x20017584 in ?? ()
(...)

The "??" indicates you don't have debug symbols installed.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-12 Thread Christian Zigotzky 
Thank you! :-)

-- Christian

Sent from my iPhone

> On 12 Feb 2017, at 08:37, Herminio Hernandez, Jr. 
>  wrote:
> 
> I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace. I 
> am posting it here.
> 
> Herminio
> 
>> On Tue, Feb 7, 2017 at 12:49 AM, Christian Zigotzky  
>> wrote:
>> Could someone also test Firefox 51.0.1-1? My gdb closes after the command 
>> 'run'.
>> 
>> -- Christian
>> 
>> Sent from my iPhone
>> 
>> > On 7 Feb 2017, at 00:09, Christian Zigotzky  wrote:
>> >
>> > Unfortunately, gdb has closed after the command 'run'. It's not possible 
>> > to get a backtrace.
>> >
>> >> On 07 February 2017 at 12:04 AM, John Paul Adrian Glaubitz wrote:
>> >>> On 02/07/2017 12:02 AM, Christian Zigotzky wrote:
>> >>> (gdb) run
>> >>>
>> >>> Starting program: /usr/lib/firefox/./firefox
>> >>> warning: Could not load shared library symbols for linux-vdso32.so.1.
>> >>> Do you need "set solib-search-path" or "set sysroot"?
>> >>> [Thread debugging using libthread_db enabled]
>> >>> Using host libthread_db library 
>> >>> "/lib/powerpc-linux-gnu/libthread_db.so.1".
>> >>> Dwarf Error: wrong version in compilation unit header (is 7, should be 
>> >>> 2, 3, or 4) [in module
>> >>> /usr/lib/debug/.build-id/18/ea31ffd1c49eaf7be933acec89325cb9e187bf.debug]
>> >>> Dwarf Error: wrong version in compilation unit header (is 0, should be 
>> >>> 2, 3, or 4) [in module
>> >>> /usr/lib/debug/.build-id/26/a1e97b21731a564ed396149593f4084391a20c.debug]
>> >>> Dwarf Error: wrong version in compilation unit header (is 0, should be 
>> >>> 2, 3, or 4) [in module
>> >>> /usr/lib/debug/.build-id/7a/f876d1dcfc23d59299dd09539d4dba3a2ec5ce.debug]
>> >>> Dwarf Error: bad offset (0x3e83) in compilation unit header (offset 
>> >>> 0x0 + 6) [in module
>> >>> /usr/lib/debug/.build-id/7c/05723a7ada75d51fd4a85a036351a976ed9a68.debug]
>> >>> Segmentation fault
>> >> And what's the backtrace?
>> >>
>> >
>> 
> 
>

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-11 Thread Herminio Hernandez, Jr. 
I ran firefox 51 on my iBook G4 running Sid. I was able to get a backtrace.
I am posting it here.

Herminio

On Tue, Feb 7, 2017 at 12:49 AM, Christian Zigotzky 
wrote:

> Could someone also test Firefox 51.0.1-1? My gdb closes after the command
> 'run'.
>
> -- Christian
>
> Sent from my iPhone
>
> > On 7 Feb 2017, at 00:09, Christian Zigotzky 
> wrote:
> >
> > Unfortunately, gdb has closed after the command 'run'. It's not possible
> to get a backtrace.
> >
> >> On 07 February 2017 at 12:04 AM, John Paul Adrian Glaubitz wrote:
> >>> On 02/07/2017 12:02 AM, Christian Zigotzky wrote:
> >>> (gdb) run
> >>>
> >>> Starting program: /usr/lib/firefox/./firefox
> >>> warning: Could not load shared library symbols for linux-vdso32.so.1.
> >>> Do you need "set solib-search-path" or "set sysroot"?
> >>> [Thread debugging using libthread_db enabled]
> >>> Using host libthread_db library "/lib/powerpc-linux-gnu/
> libthread_db.so.1".
> >>> Dwarf Error: wrong version in compilation unit header (is 7, should be
> 2, 3, or 4) [in module
> >>> /usr/lib/debug/.build-id/18/ea31ffd1c49eaf7be933acec89325c
> b9e187bf.debug]
> >>> Dwarf Error: wrong version in compilation unit header (is 0, should be
> 2, 3, or 4) [in module
> >>> /usr/lib/debug/.build-id/26/a1e97b21731a564ed396149593f408
> 4391a20c.debug]
> >>> Dwarf Error: wrong version in compilation unit header (is 0, should be
> 2, 3, or 4) [in module
> >>> /usr/lib/debug/.build-id/7a/f876d1dcfc23d59299dd09539d4dba
> 3a2ec5ce.debug]
> >>> Dwarf Error: bad offset (0x3e83) in compilation unit header
> (offset 0x0 + 6) [in module
> >>> /usr/lib/debug/.build-id/7c/05723a7ada75d51fd4a85a036351a9
> 76ed9a68.debug]
> >>> Segmentation fault
> >> And what's the backtrace?
> >>
> >
>
>


firefox.real-gdb.log
Description: Binary data

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-07 Thread Michel Dänzer 
On 07/02/17 08:04 AM, John Paul Adrian Glaubitz wrote:
> On 02/07/2017 12:02 AM, Christian Zigotzky wrote:
>> (gdb) run
>>
>> Starting program: /usr/lib/firefox/./firefox
>> warning: Could not load shared library symbols for linux-vdso32.so.1.
>> Do you need "set solib-search-path" or "set sysroot"?
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
>> Dwarf Error: wrong version in compilation unit header (is 7, should be 2, 3, 
>> or 4) [in module
>> /usr/lib/debug/.build-id/18/ea31ffd1c49eaf7be933acec89325cb9e187bf.debug]
>> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 3, 
>> or 4) [in module
>> /usr/lib/debug/.build-id/26/a1e97b21731a564ed396149593f4084391a20c.debug]
>> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 3, 
>> or 4) [in module
>> /usr/lib/debug/.build-id/7a/f876d1dcfc23d59299dd09539d4dba3a2ec5ce.debug]
>> Dwarf Error: bad offset (0x3e83) in compilation unit header (offset 0x0 
>> + 6) [in module
>> /usr/lib/debug/.build-id/7c/05723a7ada75d51fd4a85a036351a976ed9a68.debug]
>> Segmentation fault
> 
> And what's the backtrace?

Since there's no gdb prompt after the crash, the output above looks like
gdb itself crashes.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread Christian Zigotzky 
Could someone also test Firefox 51.0.1-1? My gdb closes after the command 'run'.

-- Christian

Sent from my iPhone

> On 7 Feb 2017, at 00:09, Christian Zigotzky  wrote:
> 
> Unfortunately, gdb has closed after the command 'run'. It's not possible to 
> get a backtrace.
> 
>> On 07 February 2017 at 12:04 AM, John Paul Adrian Glaubitz wrote:
>>> On 02/07/2017 12:02 AM, Christian Zigotzky wrote:
>>> (gdb) run
>>> 
>>> Starting program: /usr/lib/firefox/./firefox
>>> warning: Could not load shared library symbols for linux-vdso32.so.1.
>>> Do you need "set solib-search-path" or "set sysroot"?
>>> [Thread debugging using libthread_db enabled]
>>> Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
>>> Dwarf Error: wrong version in compilation unit header (is 7, should be 2, 
>>> 3, or 4) [in module
>>> /usr/lib/debug/.build-id/18/ea31ffd1c49eaf7be933acec89325cb9e187bf.debug]
>>> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 
>>> 3, or 4) [in module
>>> /usr/lib/debug/.build-id/26/a1e97b21731a564ed396149593f4084391a20c.debug]
>>> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 
>>> 3, or 4) [in module
>>> /usr/lib/debug/.build-id/7a/f876d1dcfc23d59299dd09539d4dba3a2ec5ce.debug]
>>> Dwarf Error: bad offset (0x3e83) in compilation unit header (offset 0x0 
>>> + 6) [in module
>>> /usr/lib/debug/.build-id/7c/05723a7ada75d51fd4a85a036351a976ed9a68.debug]
>>> Segmentation fault
>> And what's the backtrace?
>> 
>

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread John Paul Adrian Glaubitz 
On 02/07/2017 06:16 AM, Herminio Hernandez Jr.  wrote:
> Isn't there a logging feature that will capture it?

You don't get the backtrace from these logs. You need gdb for that.

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread Herminio Hernandez Jr. 
Isn't there a logging feature that will capture it?

Sent from my iPhone

> On Feb 6, 2017, at 4:09 PM, Christian Zigotzky  wrote:
> 
> Unfortunately, gdb has closed after the command 'run'. It's not possible to 
> get a backtrace.
> 
>> On 07 February 2017 at 12:04 AM, John Paul Adrian Glaubitz wrote:
>>> On 02/07/2017 12:02 AM, Christian Zigotzky wrote:
>>> (gdb) run
>>> 
>>> Starting program: /usr/lib/firefox/./firefox
>>> warning: Could not load shared library symbols for linux-vdso32.so.1.
>>> Do you need "set solib-search-path" or "set sysroot"?
>>> [Thread debugging using libthread_db enabled]
>>> Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
>>> Dwarf Error: wrong version in compilation unit header (is 7, should be 2, 
>>> 3, or 4) [in module
>>> /usr/lib/debug/.build-id/18/ea31ffd1c49eaf7be933acec89325cb9e187bf.debug]
>>> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 
>>> 3, or 4) [in module
>>> /usr/lib/debug/.build-id/26/a1e97b21731a564ed396149593f4084391a20c.debug]
>>> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 
>>> 3, or 4) [in module
>>> /usr/lib/debug/.build-id/7a/f876d1dcfc23d59299dd09539d4dba3a2ec5ce.debug]
>>> Dwarf Error: bad offset (0x3e83) in compilation unit header (offset 0x0 
>>> + 6) [in module
>>> /usr/lib/debug/.build-id/7c/05723a7ada75d51fd4a85a036351a976ed9a68.debug]
>>> Segmentation fault
>> And what's the backtrace?
>> 
>

Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread Christian Zigotzky 
Unfortunately, gdb has closed after the command 'run'. It's not possible 
to get a backtrace.


On 07 February 2017 at 12:04 AM, John Paul Adrian Glaubitz wrote:

On 02/07/2017 12:02 AM, Christian Zigotzky wrote:

(gdb) run

Starting program: /usr/lib/firefox/./firefox
warning: Could not load shared library symbols for linux-vdso32.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
Dwarf Error: wrong version in compilation unit header (is 7, should be 2, 3, or 
4) [in module
/usr/lib/debug/.build-id/18/ea31ffd1c49eaf7be933acec89325cb9e187bf.debug]
Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 3, or 
4) [in module
/usr/lib/debug/.build-id/26/a1e97b21731a564ed396149593f4084391a20c.debug]
Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 3, or 
4) [in module
/usr/lib/debug/.build-id/7a/f876d1dcfc23d59299dd09539d4dba3a2ec5ce.debug]
Dwarf Error: bad offset (0x3e83) in compilation unit header (offset 0x0 + 
6) [in module
/usr/lib/debug/.build-id/7c/05723a7ada75d51fd4a85a036351a976ed9a68.debug]
Segmentation fault

And what's the backtrace?

Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread Christian Zigotzky 

Hi Adrian,

apt-get install -t experimental firefox-dbgsym

Preparing to unpack .../firefox-dbgsym_51.0.1-1_powerpc.deb ...
Unpacking firefox-dbgsym (51.0.1-1) ...
Setting up firefox-dbgsym (51.0.1-1) ...

apt-get install -t experimental firefox-dev-dbgsym

Setting up firefox-dev (51.0.1-1) ...
Setting up firefox-dev-dbgsym (51.0.1-1) ...

It's working.

gdb ./firefox

GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/lib/firefox/firefox...Reading symbols from 
/usr/lib/debug/.build-id/a6/81b7e65ae15687f43f84f7c55dfc4626f13bda.debug...Dwarf 
Error: wrong version in compilation unit header (is 6, should be 2, 3, 
or 4) [in module 
/usr/lib/debug/.build-id/a6/81b7e65ae15687f43f84f7c55dfc4626f13bda.debug]

(no debugging symbols found)...done.
(no debugging symbols found)...done.

(gdb) run

Starting program: /usr/lib/firefox/./firefox
warning: Could not load shared library symbols for linux-vdso32.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
Dwarf Error: wrong version in compilation unit header (is 7, should be 
2, 3, or 4) [in module 
/usr/lib/debug/.build-id/18/ea31ffd1c49eaf7be933acec89325cb9e187bf.debug]
Dwarf Error: wrong version in compilation unit header (is 0, should be 
2, 3, or 4) [in module 
/usr/lib/debug/.build-id/26/a1e97b21731a564ed396149593f4084391a20c.debug]
Dwarf Error: wrong version in compilation unit header (is 0, should be 
2, 3, or 4) [in module 
/usr/lib/debug/.build-id/7a/f876d1dcfc23d59299dd09539d4dba3a2ec5ce.debug]
Dwarf Error: bad offset (0x3e83) in compilation unit header (offset 
0x0 + 6) [in module 
/usr/lib/debug/.build-id/7c/05723a7ada75d51fd4a85a036351a976ed9a68.debug]

Segmentation fault

Cheers,
Christian

On 06 February 2017 at 11:42 PM, John Paul Adrian Glaubitz wrote:

On 02/06/2017 11:36 PM, Christian Zigotzky wrote:

Which package should I install?

firefox-dbgsym should be enough. If not, installing the other
package as well shouldn't hurt either.

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread John Paul Adrian Glaubitz 
On 02/07/2017 12:02 AM, Christian Zigotzky wrote:
> (gdb) run
> 
> Starting program: /usr/lib/firefox/./firefox
> warning: Could not load shared library symbols for linux-vdso32.so.1.
> Do you need "set solib-search-path" or "set sysroot"?
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
> Dwarf Error: wrong version in compilation unit header (is 7, should be 2, 3, 
> or 4) [in module
> /usr/lib/debug/.build-id/18/ea31ffd1c49eaf7be933acec89325cb9e187bf.debug]
> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 3, 
> or 4) [in module
> /usr/lib/debug/.build-id/26/a1e97b21731a564ed396149593f4084391a20c.debug]
> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 3, 
> or 4) [in module
> /usr/lib/debug/.build-id/7a/f876d1dcfc23d59299dd09539d4dba3a2ec5ce.debug]
> Dwarf Error: bad offset (0x3e83) in compilation unit header (offset 0x0 + 
> 6) [in module
> /usr/lib/debug/.build-id/7c/05723a7ada75d51fd4a85a036351a976ed9a68.debug]
> Segmentation fault

And what's the backtrace?

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread John Paul Adrian Glaubitz 
On 02/06/2017 11:36 PM, Christian Zigotzky wrote:
> Which package should I install?

firefox-dbgsym should be enough. If not, installing the other
package as well shouldn't hurt either.

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread John Paul Adrian Glaubitz 
On 02/06/2017 11:30 PM, John Paul Adrian Glaubitz wrote:
> Debug packages are delivered through different mirrors these days.
> 
> Try this: https://wiki.debian.org/AutomaticDebugPackages

Note: The name of the debug package changes to "firefox-dbgsym".

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread Christian Zigotzky 

Adrian,

Thanks for your hint.

apt-get install -t experimental firefox-dbg
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package firefox-dbg is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  firefox-dev-dbgsym firefox-dbgsym

---

Which package should I install?

Cheers,
Christian

On 06 February 2017 at 11:30 PM, John Paul Adrian Glaubitz wrote:

On 02/06/2017 11:28 PM, Christian Zigotzky wrote:

There isn't a firefox-dbg package available.

Debug packages are delivered through different mirrors these days.

Try this: https://wiki.debian.org/AutomaticDebugPackages

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread John Paul Adrian Glaubitz 
On 02/06/2017 11:28 PM, Christian Zigotzky wrote:
> There isn't a firefox-dbg package available.

Debug packages are delivered through different mirrors these days.

Try this: https://wiki.debian.org/AutomaticDebugPackages

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread Christian Zigotzky 

There isn't a firefox-dbg package available.

My sources.list (/etc/apt/sources.list):

deb http://ftp.us.debian.org/debian experimental main
deb http://ftp.de.debian.org/debian/ unstable main contrib non-free

Christian

On 06 February 2017 at 11:02 PM, John Paul Adrian Glaubitz wrote:

On 02/06/2017 10:39 PM, Christian Zigotzky wrote:

bt

#0  0x1b1f5484 in ?? () from /usr/lib/firefox/libxul.so
#1  0x1b1f5448 in ?? () from /usr/lib/firefox/libxul.so
#2  0x in ?? ()

A backtrace without the Firefox debug package (firefox-dbg) isn't particularly
useful. You might want to do that first, then try again with gdb.

Adrian

Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread Christian Zigotzky 

Hi Adrian,

Thanks for the hint. I am still learning. :-)

Cheers,
Christian

On 02/06/17 at 11:02 PM, John Paul Adrian Glaubitz wrote:

On 02/06/2017 10:39 PM, Christian Zigotzky wrote:

bt

#0  0x1b1f5484 in ?? () from /usr/lib/firefox/libxul.so
#1  0x1b1f5448 in ?? () from /usr/lib/firefox/libxul.so
#2  0x in ?? ()

A backtrace without the Firefox debug package (firefox-dbg) isn't particularly
useful. You might want to do that first, then try again with gdb.

Adrian

Re: Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread John Paul Adrian Glaubitz 
On 02/06/2017 10:39 PM, Christian Zigotzky wrote:
> bt
> 
> #0  0x1b1f5484 in ?? () from /usr/lib/firefox/libxul.so
> #1  0x1b1f5448 in ?? () from /usr/lib/firefox/libxul.so
> #2  0x in ?? ()

A backtrace without the Firefox debug package (firefox-dbg) isn't particularly
useful. You might want to do that first, then try again with gdb.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Firefox 51.0.1-1 on Debian Sid/experimental PowerPC (PPC32): Segmentation fault

2017-02-06 Thread Christian Zigotzky 

Hi All,

I installed Firefox 51.0.1-1 with 'apt-get install -t experimental 
firefox' on Debian Sid/experimental PowerPC (PPC32) today.


System: AmigaOne X1000 (Nemo board with P.A. Semi PA6T-1682M CPU)

Unfortunately it doesn't start.

Error messages:

Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 
1 (t=7.9707) |[16][GFX1]: Unknown image format 0 (t=8.05967) 
|[17][GFX1]: Unknown image format 0 (t=8.06025) |[18][GFX1]: Unknown 
image format 0 (t=8.06058) |[4][GFX1]: Unknown image format 0 
(t=8.00356) |[5][GFX1]: Unknown image format 0 (t=8.00627) |[6][GFX1]: 
Unknown image format 0 (t=8.00842) |[7][GFX1]: Unknown image format 0 
(t=8.01168) |[8][GFX1]: Unknown image format 0 (t=8.01233) |[9][GFX1]: 
Unknown image format 0 (t=8.01551) |[10][GFX1]: Unknown image format 0 
(t=8.01872) |[11][GFX1]: Unknown image format 0 (t=8.02126) |[12][GFX1]: 
Unknown image format 0 (t=8.02159) |[13][GFX1]: Unknown image format 1 
(t=8.05182) |[14][GFX1]: Unknown image format 0 (t=8.05589) |[15][GFX1]: 
Unknown image format 0 (t=8.05829) [GFX1]: Unknown image format 0

Segmentation fault

gdb /usr/lib/firefox/firefox

(gdb) run

Starting program: /usr/lib/firefox/firefox
warning: Could not load shared library symbols for linux-vdso32.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
[New Thread 0xf7cff460 (LWP 4770)]
[New Thread 0xf5f3a460 (LWP 4771)]
[Thread 0xf5f3a460 (LWP 4771) exited]
[New Thread 0xf5f3a460 (LWP 4772)]
[New Thread 0xf4b8f460 (LWP 4773)]
[New Thread 0xf41ff460 (LWP 4774)]
[New Thread 0xf39ff460 (LWP 4775)]
[New Thread 0xf31ff460 (LWP 4776)]
[New Thread 0xf29ff460 (LWP 4777)]
[New Thread 0xf21ff460 (LWP 4778)]
[New Thread 0xf19ff460 (LWP 4779)]
[New Thread 0xf0de9460 (LWP 4780)]
[New Thread 0xf05e9460 (LWP 4781)]
[New Thread 0xefde9460 (LWP 4782)]
[New Thread 0xef5e9460 (LWP 4783)]
[New Thread 0xeede9460 (LWP 4784)]
[New Thread 0xf438f460 (LWP 4785)]
[New Thread 0xee0ff460 (LWP 4786)]
[New Thread 0xed4ff460 (LWP 4787)]
[New Thread 0xec058460 (LWP 4788)]
[New Thread 0xeb858460 (LWP 4789)]
[New Thread 0xeacff460 (LWP 4790)]
[New Thread 0xea4ff460 (LWP 4791)]
[New Thread 0xe9cff460 (LWP 4792)]
[New Thread 0xe94ff460 (LWP 4793)]
[New Thread 0xe8cff460 (LWP 4794)]
[New Thread 0xdc1ff460 (LWP 4795)]
[New Thread 0xdb9ff460 (LWP 4796)]
[New Thread 0xdafff460 (LWP 4797)]
[New Thread 0xda7ff460 (LWP 4798)]
[New Thread 0xd9fff460 (LWP 4799)]
[New Thread 0xd97ff460 (LWP 4800)]
[Thread 0xdafff460 (LWP 4797) exited]
[Thread 0xda7ff460 (LWP 4798) exited]
[Thread 0xd9fff460 (LWP 4799) exited]
[New Thread 0xd8eff460 (LWP 4801)]
[Thread 0xd97ff460 (LWP 4800) exited]
[New Thread 0xd86ff460 (LWP 4802)]
[New Thread 0xd97ff460 (LWP 4803)]
[Thread 0xd97ff460 (LWP 4803) exited]
[New Thread 0xd97ff460 (LWP 4804)]
[New Thread 0xd9fff460 (LWP 4805)]
[New Thread 0xda7ff460 (LWP 4806)]
[Thread 0xeb858460 (LWP 4789) exited]
[Thread 0xd97ff460 (LWP 4804) exited]
[Thread 0xda7ff460 (LWP 4806) exited]
[New Thread 0xda7ff460 (LWP 4807)]
[Thread 0xd9fff460 (LWP 4805) exited]
[New Thread 0xd9fff460 (LWP 4808)]
[New Thread 0xd97ff460 (LWP 4809)]
Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 
1 (t=9.90193) [GFX1]: Unknown image format 1
Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 
1 (t=9.90193) |[1][GFX1]: Unknown image format 0 (t=9.95512) [GFX1]: 
Unknown image format 0
Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 
1 (t=9.90193) |[1][GFX1]: Unknown image format 0 (t=9.95512) |[2][GFX1]: 
Unknown image format 0 (t=9.95534) [GFX1]: Unknown image format 0
Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 
1 (t=9.90193) |[1][GFX1]: Unknown image format 0 (t=9.95512) |[2][GFX1]: 
Unknown image format 0 (t=9.95534) |[3][GFX1]: Unknown image format 0 
(t=9.95551) [GFX1]: Unknown image format 0
Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 
1 (t=9.90193) |[1][GFX1]: Unknown image format 0 (t=9.95512) |[2][GFX1]: 
Unknown image format 0 (t=9.95534) |[3][GFX1]: Unknown image format 0 
(t=9.95551) |[4][GFX1]: Unknown image format 0 (t=9.95569) [GFX1]: 
Unknown image format 0
Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 
1 (t=9.90193) |[1][GFX1]: Unknown image format 0 (t=9.95512) |[2][GFX1]: 
Unknown image format 0 (t=9.95534) |[3][GFX1]: Unknown image format 0 
(t=9.95551) |[4][GFX1]: Unknown image format 0 (t=9.95569) |[5][GFX1]: 
Unknown image format 0 (t=9.95588) [GFX1]: Unknown image format 0
Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 
1 (t=9.90193) |[1][GFX1]: Unknown image format 0 (t=9.95512) |[2][GFX1]: 
Unknown image format 0 (t=9.95534) |[3][GFX1]: Unknown image format 0 
(t=9.95551) |[4][GFX1]: Unknown image format 0 (t=9.95569) |[5][GFX1]: 
Unknown image format 0 (t=9.95588) |[6][GFX1]: Unk