Author chaselton
Recipients chaselton, freakboy3742, mpaolini, r.david.murray, refi64, tritium
Date 2015-11-01.14:34:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446388461.22.0.596296765282.issue23496@psf.upfronthosting.co.za>
In-reply-to
Content
GDB debugging isn't going to happen any time soon; all of the gdb tests fail.
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 (https://mail.python.org/pipermail/python-bugs-list/2015-March/267442.html)
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.
History
Date User Action Args
2015-11-01 14:34:21chaseltonsetrecipients: + chaselton, r.david.murray, freakboy3742, refi64, mpaolini, tritium
2015-11-01 14:34:21chaseltonsetmessageid: <1446388461.22.0.596296765282.issue23496@psf.upfronthosting.co.za>
2015-11-01 14:34:21chaseltonlinkissue23496 messages
2015-11-01 14:34:21chaseltoncreate