http://bugzilla.novell.com/show_bug.cgi?id=513921
User jmatejek@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=513921#c18
Jan Matejek
please try the following: - compile the module without optimizations and see if that helps
I compiled Xen's libxc python extension (xc.so) with "-g -O0" and was then able to start a vm. So without optimizations the problem doesn't appear.
"without optimizations the problem doesn't appear" = miscompilation of the module which means that either you hit a gcc bug, or there is some undefined behavior used in the affected functions. valgrind won't be of any use here, and i won't be able to help much too. you said earlier that (In reply to comment #14)
Adding print statements in pyxc_dom_set_policy_cpuid also showed successful returns but had the side effect of no longer seeing the python exception.
please try doing that again (with the optimized version, of course) and post a diff of what you've done to make the exception go away. at that point it will be easy for somebody from gcc team to tell us either that we need to fix something (and what), or that they need to fix something -- 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.