[Stackless] A new crash bug

Werner Thie wthie at thiengineering.ch
Tue Oct 16 08:12:20 CEST 2007


Hi all

Since you mention using the 2005 express release, did you use any one of 
the backward release #defines like

_USE_32BIT_TIME_T
_CRT_SECURE_NO_DEPRECATE

and friends when compiling? I recently had to port over some code from 
MSDEV2003/VC7 to MSDEV2005/VC8 and was quite surprised, at how much MS 
changed and adapted in between those two releases of their tools. 
Specially the silent adaptions in the 64bit pointer departement are 
difficult to catch, usually the only thing you see is a port mortem and 
a mention of stack corruption.

Werner

Carlos Eduardo de Paula wrote:
> It crashes for me here... using WindowsXP.
> 
> Python 2.5.1 Stackless 3.1b3 060516 (release25-maint:55039:55048, May
> 1 2007, 14:13:4) [MSC v.1310 32 bit (Intel)] on win32
> Type "help", "copyright", "credits" or "license" for more information.
> 
> 
> Carlos
> 
> 
> On 10/15/07, Richard Tew <richard.m.tew at gmail.com> wrote:
>> On 10/15/07, Kristján Valur Jónsson <kristjan at ccpgames.com> wrote:
>>> I don't get it to crash, debug or release.
>>> What exact command line are you using?  Since you mention GC, maybe GC needs to trigger in a particular place?  Will adding a gc.collect() in a strategic place help it to crash?
>> I have it in the Stackless unittest directory in my local SVN
>> checkout, as test_blah.py.  Then I invoke it with '"c:\program
>> files\python251\python.exe" test_blah.py'.  It is the standard Python
>> 2.5.1 install from python.org and the 2.5.1 Stackless dlls which are
>> available from stackless.com.
>>
>> The reproduction case is 100% reliable with this setup.  I cannot
>> debug it as I do not own Visual Studio and freshly reinstalled Vista
>> recently losing my install of Visual Studio 2005 Express.  Assuming it
>> happens with VS 2005 Express.  But anyone who is using the provided
>> builds of Stackless for 2.5.1 should be vulnerable to this bug, as
>> they would be using the exact same setup of course.
>>
>> Anyway, perhaps it is not worth bothering with.  If no-one else is
>> experiencing it, then it might be either my use of Vista, or the fact
>> I compiled the distribution dlls with the freely available 'MS
>> toolkit' version of VS 2003, which is causing the problem.
>>
>> Richard.
>>
>> _______________________________________________
>> Stackless mailing list
>> Stackless at stackless.com
>> http://www.stackless.com/mailman/listinfo/stackless
>>
> 
> 




More information about the Stackless mailing list