"Bad MAGIC!" about pycdc HOT 5 CLOSED

That message indicates that the magic number (first 4 bytes of the pyc file) wasn't recognized... Since the .pyc files included in the tests directory are known to work at least far enough to decode the magic number, I suspect something is odd about compilation with VS2012, but I haven't been able to reproduce it so far (I tried with the VS 2012 platform toolset in both x86 and x64 targets). Please verify that your .pyc files aren't corrupt, and provide more details on your configuration.

from pycdc.

Confirming

Compiled with VC++2008 Express

K:\Documents and Settings\Administrator\Desktop\wot\dec\pycdc\bin>pycdas.exe ..\tests\15_test_class.pyc
Bad MAGIC!
15_test_class.pyc (Python -1.-1)
<TYPE: 48>

K:\Documents and Settings\Administrator\Desktop\wot\dec\pycdc\bin>pycdas.exe ..\tests\15_test_expressions.pyc
Bad MAGIC!
15_test_expressions.pyc (Python -1.-1)
<TYPE: 48>

K:\Documents and Settings\Administrator\Desktop\wot\dec\pycdc\bin>pycdas.exe ..\tests\22_class_method.pyc
Bad MAGIC!
22_class_method.pyc (Python -1.-1)
<TYPE: 48>

K:\Documents and Settings\Administrator\Desktop\wot\dec\pycdc\bin>pycdas.exe ..\tests\26_if_elif_else.pyc
Bad MAGIC!
26_if_elif_else.pyc (Python -1.-1)
<TYPE: 48>

K:\Documents and Settings\Administrator\Desktop\wot\dec\pycdc\bin>pycdas.exe ..\tests\31_while_loops.pyc
Bad MAGIC!
31_while_loops.pyc (Python -1.-1)
<TYPE: 48>

from pycdc.

Compiled with vc++2008 Debug mode is ok,
Release mode getting Bad MAGIC!

from pycdc.

vc++2008 with Debug mode produced garbage .exe files for me (“Program is not a recognized executable”) :(

from pycdc.

It turns out that newer versions of VS will re-order the getByte() calls in Release mode, but not Debug mode. This is why I couldn't reproduce it before :(. I'm creating a fix now

from pycdc.