[Python-Dev] Newly Built Python3 Binary Throws Segfault
chaselton at gmail.com
Wed Jan 28 17:34:04 CET 2015
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> wrote:
> There could be a million differences relevant (unicode, ints, ...). Perhaps
> 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> wrote:
>> 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,
>> Python-Dev mailing list
>> Python-Dev at python.org
> --Guido van Rossum (python.org/~guido)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 9149 bytes
Desc: not available
More information about the Python-Dev