Hi.
Do you get this only with the installed version?
Could you try replacing it with your own build?  If so, could you go into the 
source code and disable stack spilling ?
You have to nerf the macro CSTACK_SAVE_NOW.

I saw some mysterious crashes recently in a live build in Shanghai that went 
away when I disabled this.

K

> -----Original Message-----
> From: [email protected] [mailto:stackless-
> [email protected]] On Behalf Of Richard Tew
> Sent: 3. febrúar 2014 03:04
> To: [email protected]
> Subject: [Stackless] Windows 2.7.6 stability
> 
> Hi,
> 
> I've got the installer we provide for 2.7.6, on Windows.  And I've been 
> getting
> lots of non-crashing premature exits:
> 
> SystemError: unknown opcode
> XXX lineno: 314, opcode: 0
> 
> It's not consistently reproducible using running the same code, but can be
> sometimes, and I'm not using any Stackless features.
> 
> If I take the mainline python repo and sync to v2.7.6 and generate a dll, and
> put it in c:\python27, all the problems go away.
> 
> I thought it might be pyside 1.1.2 which I was using, but upgraded that and
> the problem remained with pyside 1.2.1.  That's the only external
> dependency my code uses.
> 
> Anyone else using this installer?
> 
> Cheers,
> Richard.
> 
> _______________________________________________
> Stackless mailing list
> [email protected]
> http://www.stackless.com/mailman/listinfo/stackless



_______________________________________________
Stackless mailing list
[email protected]
http://www.stackless.com/mailman/listinfo/stackless

Reply via email to