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
Da: Lennart Sorensen <lsore...@csclub.uwaterloo.ca>
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
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.
-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.
>
Στις 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
>
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
Στις 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
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
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
It means all are killing us in all fronts.
[☹]
Luigi
Da: John Paul Adrian Glaubitz <glaub...@physik.fu-berlin.de>
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
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
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
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
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/
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
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
>
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.
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
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
>
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
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 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
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,
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
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) ...
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
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
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
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
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 -
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
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
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
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:
34 matches
Mail list logo