[Python-Dev] Newly Built Python3 Binary Throws Segfault
rymg19 at gmail.com
Wed Jan 28 18:23:53 CET 2015
On Wed, Jan 28, 2015 at 10:43 AM, Guido van Rossum <guido at python.org> wrote:
> What I see in the strace:
> ... load libpython3.4m.so.1.0
> ... load libm
> ... open /dev/__properties__ and do something to it (what?)
> ... get current time
> ... allocate memory
> ... getuid
> ... segfault
> That's not a lot to go on, but it doesn't look as if it has started to
> load modules yet.
> Does /dev/__properties__ ring a bell? Not to me.
is the code that works with that file.
it a bit (slides 24-29). Looks like something to do with interprocess
communication. Likely has nothing to do with Python itself.
> That stack trace would be really helpful.
> On Wed, Jan 28, 2015 at 8:34 AM, Cyd Haselton <chaselton at gmail.com> wrote:
>> Apologies...I'm not sure what a stack track is, but I do have the
>> strace. Nearest I can tell, it happens due to an open call, though I
>> am probably wrong.
>> Attaching the strace output to this email. I'm going to head back to
>> the documentation and to back out of some Android-related changes in
>> On Wed, Jan 28, 2015 at 9:43 AM, Guido van Rossum <guido at python.org>
>> > There could be a million differences relevant (unicode, ints, ...).
>> > the importlib bootstrap is failing. Perhaps the dynamic loading code
>> > changed. Did you get a stack track? (IIRC strace shows a syscall trace
>> > also useful, but doesn't tell you precisely how it segfaulted.)
>> > On Wed, Jan 28, 2015 at 6:43 AM, Cyd Haselton <chaselton at gmail.com>
>> >> All,
>> >> I recently ditched my attempts to port Python 2.7.8 to Android in
>> >> favor of Python 3.4.2. Unfortunately, after using the same configure
>> >> options in the same environment, and modifying the setup.py as needed,
>> >> the newly built binary throws a segfault when the generate-posix-vars
>> >> portion of the build is reached...and when it is run as well (i.e.
>> >> ./python --help, ./python -E -S -m sysconfig, or similar)
>> >> I took a strace of ./python, however I'm a bit lost when reviewing it.
>> >> Any ideas as to what may be going on...i.e. why Python 2.7 works but
>> >> 3.x throws a segfault?
>> >> Thanks in advance,
>> >> Cyd
>> >> _______________________________________________
>> >> Python-Dev mailing list
>> >> Python-Dev at python.org
>> >> https://mail.python.org/mailman/listinfo/python-dev
>> >> Unsubscribe:
>> >> https://mail.python.org/mailman/options/python-dev/guido%40python.org
>> > --
>> > --Guido van Rossum (python.org/~guido)
> --Guido van Rossum (python.org/~guido)
> Python-Dev mailing list
> Python-Dev at python.org
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
"It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
Personal reality distortion fields are immune to contradictory evidence. -
Check out my website: http://kirbyfan64.github.io/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev