This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author refi64
Recipients chaselton, ethan.furman, freakboy3742, r.david.murray, refi64
Date 2015-06-29.14:00:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <A2B81B1C-BA0A-49B5-A1E1-95EA7C21CDBA@gmail.com>
In-reply-to <1435579764.95.0.771671035101.issue23496@psf.upfronthosting.co.za>
Content
You compiled with -fPIE and GCC, right? I know the Android Clang seems broken.

On June 29, 2015 7:09:25 AM CDT, Cyd Haselton <report@bugs.python.org> wrote:
>
>Cyd Haselton added the comment:
>
>FYI, Figured out that running ./configure with --with-pydebug does NOT
>define Py_DEBUG in pyconfig.h.
>
>Defining it in pyconfig.h got me past the "undefined reference to
>`_PyUnicode_CheckConsistency'" error, but i'm now getting this:
>
>if test $? -ne 0 ; then \
>        echo "generate-posix-vars failed" ; \
>        rm -f ./pybuilddir.txt ; \
>        exit 1 ; \
>fi
>Debug memory block at address p=0x90b7b0: API ''
>    2416312320 bytes originally requested
>    The 3 pad bytes at p-3 are not all FORBIDDENBYTE (0xfb):
>        at p-3: 0x00 *** OUCH
>        at p-2: 0x00 *** OUCH
>        at p-1: 0x00 *** OUCH
> Because memory is corrupted at the start, the count of bytes requested
>       may be bogus, and checking the trailing pad bytes may segfault.
>    The 4 pad bytes at tail=0x9096b7b0 are Segmentation fault
>generate-posix-vars failed
>make: *** [pybuilddir.txt] Error 1
>
>Will re-check patch application and try again
>
>----------
>
>_______________________________________
>Python tracker <report@bugs.python.org>
><http://bugs.python.org/issue23496>
>_______________________________________
History
Date User Action Args
2015-06-29 14:00:01refi64setrecipients: + refi64, r.david.murray, freakboy3742, ethan.furman, chaselton
2015-06-29 14:00:01refi64linkissue23496 messages
2015-06-29 14:00:00refi64create