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 tim.peters
Recipients kristjan.jonsson, lemburg, ncoghlan, tim.peters
Date 2009-09-06.09:48:55
SpamBayes Score 7.927281e-06
Marked as misclassified No
Message-id <1252230539.27.0.0539255315852.issue6836@psf.upfronthosting.co.za>
In-reply-to
Content
Yup, it's a good idea.  In fact, storing info in the debug malloc blocks
to identify the API family used was part of "the plan", but got dropped
when time ran out.

serialno should not be abused for this purpose, though.  On a 32-bit
box, a 24-bit real serialno is too small.  Mucking with serialno also
breaks the current straightforward use of data breakpoints (under
systems that support those) to rerun a deterministic program until a
specific value for serialno is reached.

The original intent was to use one of "forbidden" pad bytes for this
purpose, either the last one following the block or the first one
preceding the block.  That wouldn't interfere with anything, and the
code would be substantially simpler (no endless shifting and masking
needed when a byte's worth of data is stored /in/ a byte).

In any case, internal comments must document the possible values for the
"id" and their meanings.  It's just plain cruel to make the code reader
leap all over the code trying to reverse-engineer the intent ;-)
History
Date User Action Args
2009-09-06 09:48:59tim.peterssetrecipients: + tim.peters, lemburg, ncoghlan, kristjan.jonsson
2009-09-06 09:48:59tim.peterssetmessageid: <1252230539.27.0.0539255315852.issue6836@psf.upfronthosting.co.za>
2009-09-06 09:48:57tim.peterslinkissue6836 messages
2009-09-06 09:48:56tim.peterscreate