2009/10/16 atex.way <[email protected]>: > compiling and running stackless python 3.1.1 success with > "generate debug info" set yes on ms vs8 express edition, but if set > "generate debug info" to no, could compile success but cracked (assert > (opcode == FOR_ITER) exception ) in running no mater with release or debug > compiling mode. > > ... > but, further found: "eliminate unreferenced data" or > "Remove Redundant COMDATs " should be real reason for the crack of > stackless python. that it is, can't do linking optimization. > the original python source is very stable, has no this like problem. i > just want to know this question is related to c compiler or stackless codes, > because i like python, also stackless... > appreciate your answer in advance. thank you.
Sorry for the delay. I have no idea what the cause of this is but I would lean towards it being C compiler related. If the only difference between the problem occurring and not occurring is the toggling of an optimisation option, then this would be the most likely case. Cheers, Richard. _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
