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, freakboy3742, mpaolini, r.david.murray, refi64, tritium
Date 2015-11-01.15:14:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
Are there no binaries?

Pretty sure it isn't your device. I'd think a compiler issue. What are you using, and what version?

You have insane determination! :D

On November 1, 2015 8:34:21 AM CST, Cyd Haselton <> wrote:
>Cyd Haselton added the comment:
>GDB debugging isn't going to happen any time soon; all of the gdb tests
>I re-compiled with the --with-pydebug option, thinking that would help,
>but it won't build; I get the following error when the newly built
>python starts to build packages:
>Debug memory block at address p=0xb6003070: API 'a'
>    795107700 bytes originally requested
>    The 3 pad bytes at p-3 are not all FORBIDDENBYTE (0xfb):
>        at p-3: 0x2f *** 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=0xe56491e4 are Segmentation fault
>generate-posix-vars failed
>Additional things I've attemptedto try to resolve the test_hash
>failure, based on this  bug report
>1) compiling with -mno-unaligned-access
>2) compiling with FNV as the default hash algorithm.
>Neither worked. At this point I am at a loss and am beginning to think
>there may be a problem with my device.  Any suggestions are welcome.
>Python tracker <>
Date User Action Args
2015-11-01 15:14:17refi64setrecipients: + refi64, r.david.murray, freakboy3742, mpaolini, chaselton, tritium
2015-11-01 15:14:17refi64linkissue23496 messages
2015-11-01 15:14:17refi64create