http://bugzilla.novell.com/show_bug.cgi?id=513921
User jmatejek@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=513921#c15
Jan Matejek changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
CC| |jmatejek@novell.com
Info Provider|jmatejek@novell.com |
--- Comment #15 from Jan Matejek 2009-09-10 07:48:35 MDT ---
hi,
"unknown opcode" can only happen when python is executing bytecode. so unless
there is some kind of memory corruption in the C module, it won't affect it
(might be interesting to try and run it through valgrind - but please use
python's valgrind suppressions, otherwise you'll die from what you will see ;)
).
that means that either
a) python or the module is miscompiled and produces this exception elsewhere
(those debug print statements charles mentioned might suggest that)
b) there is a python bug that causes it to miscompile its own bytecode under
some circumstances, or some memory corruption that causes it to break it later
c) the .pyc or .pyo files are corrupted - you did try to remove them and run
without them, didn't you?
i would try to reproduce this, but right now i'm rather busy with studio. so
please try the following:
- compile the module without optimizations and see if that helps
- run with valgrind (read
http://svn.python.org/projects/python/trunk/Misc/README.valgrind for that)
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.