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 florin.papa
Recipients florin.papa, pitrou, r.david.murray, rhettinger, skrah, vstinner, zach.ware
Date 2015-10-08.09:29:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444296579.84.0.74729825377.issue25300@psf.upfronthosting.co.za>
In-reply-to
Content
No modifications need to be made to the small object allocator. The malloc situation was just an example, it does not mean that setting pointer bounds occurs only in a malloc call. It also occurs when you declare a static array or when you initialize a new pointer:

int *x = (int*)malloc(10 * sizeof(int));
int *y = x; // the bounds for x will be passed on to y

When using "fcheck-pointer-bounds -mmpx" _all_ memory accesses will be instrumented.
History
Date User Action Args
2015-10-08 09:29:39florin.papasetrecipients: + florin.papa, rhettinger, pitrou, vstinner, r.david.murray, skrah, zach.ware
2015-10-08 09:29:39florin.papasetmessageid: <1444296579.84.0.74729825377.issue25300@psf.upfronthosting.co.za>
2015-10-08 09:29:39florin.papalinkissue25300 messages
2015-10-08 09:29:39florin.papacreate