[issue14354] Crash in _ctypes_alloc_callback

2012-03-20 Thread Joe Rumsey
Joe Rumsey added the comment: It's maybe not directly relevant to fixing this, but I worked around it on the project where this came up by redefining dice as (c_int * 4) and col as (c_uint8 * 3) in the union, then using ctypes.cast to get those as pointers to the actual struct. That

[issue14354] Crash in _ctypes_alloc_callback

2012-03-17 Thread Joe Rumsey
Joe Rumsey added the comment: Thanks for that. This does seem to be the case. I rebuilt with CC=gcc-4.2 and my short sample and the full library I took it from both work fine. -- ___ Python tracker <http://bugs.python.org/issue14

[issue14354] Crash in _ctypes_alloc_callback

2012-03-17 Thread Joe Rumsey
Joe Rumsey added the comment: I just built python 3.2.2 from source, and reproduced the issue there as well. Same location. Here's the slightly more informative stack trace from my release-with-symbols 3.2.2 build: #0 _ctypes_alloc_callback (callable=0x7fff5fbfef20, converters=0x1000

[issue14354] Crash in _ctypes_alloc_callback

2012-03-17 Thread Joe Rumsey
New submission from Joe Rumsey : I have reproduced this crash in Apple's default 2.7.1 python, and in 2.7.3 built from source myself. But only in release mode. If I rebuild 2.7.3 in debug, the crash goes away. The attached file reproduces the issue, which has to do with a union conta