From: Josh Kropf <josh@slashdev.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: python-lang causing Alignment trap and Segfault
Date: Sat, 23 Jan 2010 15:21:29 -0500 [thread overview]
Message-ID: <4B5B5A49.3090902@slashdev.ca> (raw)
In-Reply-To: <4FB2ADE2-A098-464D-9022-E1844CDDB2DF@vanille-media.de>
Looks like the atexit module
root@mini2440:~# python -v
[snip]
# /usr/lib/python2.6/atexit.pyo matches /usr/lib/python2.6/atexit.py
import atexit # precompiled from /usr/lib/python2.6/atexit.pAlignment
trap: python (2329) PC=0x403f007c Instr=0x28001c05 Address=0xffffffff
FSR 0x813
yo
On 01/23/2010 03:09 PM, Dr. Michael Lauer wrote:
> Try running python -v to find out exactly which module is triggering
> that.
>
> Cheers,
>
> :M:
>
> Am 23.01.2010 um 20:45 schrieb Josh Kropf <josh@slashdev.ca>:
>
>> I've compiled an image for my mini2440 board (armv4t) from the
>> stable/2009 branch in git using angstrom distribution.
>>
>> One of the python packages I need depends on python-lang but I'm
>> finding that python segfaults when python-lang is installed. The
>> kernel logs the following before the segfault:
>>
>> Alignment trap: python (2303) PC=0x403f007c Instr=0x28001c05
>> Address=0xffffffff FSR 0x813
>>
>> Removing python-lang package makes python work again.
>>
>> Just wondering if anyone has run into this problem or has some
>> pointers on debugging this.
>>
>> Thanks,
>> - Josh
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-01-23 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 19:45 python-lang causing Alignment trap and Segfault Josh Kropf
2010-01-23 20:09 ` Dr. Michael Lauer
2010-01-23 20:21 ` Josh Kropf [this message]
2010-02-24 18:00 ` Josh Kropf
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=4B5B5A49.3090902@slashdev.ca \
--to=josh@slashdev.ca \
--cc=openembedded-devel@lists.openembedded.org \
/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