From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Illegal instruction by python's xmlrpclib on powerpc64, gcc-4.9
Date: Tue, 3 Nov 2015 16:20:36 -0300 [thread overview]
Message-ID: <56390904.7010101@zacarias.com.ar> (raw)
In-Reply-To: <20151103151730.1e9dcc3c@free-electrons.com>
On 03/11/15 11:17, Thomas Petazzoni wrote:
> Dear Alvaro Gamez,
>
> Adding in Cc: some PowerPC folks: Gustavo Zacarias who added the 6500
> config option, and Cody who added the initial PowerPC64 support.
> Gustavo, Cody, can you look below ?
>
> Alvaro, read only below for some suggestions.
>
> Thanks!
>
> Thomas
>
> Can you rebuild with BR2_ENABLE_DEBUG=y, then run "ulimit -c unlimited"
> on your target, run the crashing Python stuff, grab back the "core"
> file on your host machine, and 1 /look at the backtrace and 2/ at the
> specific instruction that caused the crash ?
>
> This would probably help quite a bit I believe.
>
> Thanks a lot!
>
> Thomas
Hi All.
I've added e5500/e6500 support with basic testing from Dwayne Fontenot,
i never had any e5500/6500 hardware in my hands to test though, so it's
kind of YMMV/best spare effort.
Testing with qemu_ppc64_pseries_defconfig which is the closest i can get
seems to have no issues importing xmlrpclib, so a wild guess is that the
toolchain has some bug with e6500 code generation, likely gcc.
Having a backtrace might help pinpoint a bit better, trying varying
toolchain component versions would be a random test if not.
Regards.
next prev parent reply other threads:[~2015-11-03 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 9:40 [Buildroot] Illegal instruction by python's xmlrpclib on powerpc64, gcc-4.9 Alvaro Gamez
2015-11-03 14:17 ` Thomas Petazzoni
2015-11-03 19:20 ` Gustavo Zacarias [this message]
2015-11-03 19:25 ` Thomas Petazzoni
2015-11-04 10:18 ` Alvaro Gamez
2015-11-04 10:49 ` Thomas Petazzoni
2015-11-04 11:31 ` Alvaro Gamez
2015-11-04 15:24 ` Alvaro Gamez
2015-11-04 22:48 ` Arnout Vandecappelle
2015-11-05 10:27 ` Alvaro Gamez
2015-11-05 11:13 ` Arnout Vandecappelle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56390904.7010101@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox