Message 124700 - Python tracker

➜

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.

In-reply-to
Author	kristjan.jonsson
Recipients	amaury.forgeotdarc, kristjan.jonsson, theller
Date	2010年12月27日.02:42:37
SpamBayes Score	0.00077222794
Marked as misclassified	No
Message-id	<1293417759.36.0.171437051543.issue10296@psf.upfronthosting.co.za>

Content
I _think_ that in our old 2.5 python (which had a backported ctypes from 2.6 to support 64 bits) we always got the JIT debugger i.e. with _ctypes.pyd and _ctypes_d.pyd. This api, "DebugBreak" always invokes the JIT debugger, however the program was compiled (_NDEBUG, DEBUG, or not). This is done by raising the breakpoint exception and apparently _ctypes.pyd is catching that exception and handling it, but only in release mode, while I think it shouldn't do.

Content

I _think_ that in our old 2.5 python (which had a backported ctypes from 2.6 to support 64 bits) we always got the JIT debugger i.e. with _ctypes.pyd and _ctypes_d.pyd.
This api, "DebugBreak" always invokes the JIT debugger, however the program was compiled (_NDEBUG, DEBUG, or not).
This is done by raising the breakpoint exception and apparently _ctypes.pyd is catching that exception and handling it, but only in release mode, while I think it shouldn't do.

History
Date	User	Action	Args
2010年12月27日 02:42:39	kristjan.jonsson	set	recipients: + kristjan.jonsson, theller, amaury.forgeotdarc
2010年12月27日 02:42:39	kristjan.jonsson	set	messageid: <1293417759.36.0.171437051543.issue10296@psf.upfronthosting.co.za>
2010年12月27日 02:42:37	kristjan.jonsson	link	issue10296 messages
2010年12月27日 02:42:37	kristjan.jonsson	create

homepage