Good idea - it's not the valgrind include, anyway.
(valgrind 1.0.4, optimized pike with everything but no special include)
| disInstr: unhandled opcode 0xCC then 0x5 | | valgrind: the `impossible' happened: | unhandled x86 opcode | Basic block ctr is approximately 6100000 | | sched status: | | Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 | ==22864== at 0x2DA60654: ??? | ==22864== by 0x2E0246D1: ??? | ==22864== by 0x8071427: apply_low_safe_and_stupid (in /home/mirar/pike/orchid/test-install/pike/7.5.1/bin/pike) | ==22864== by 0x812CAC9: eval_low (in /home/mirar/pike/orchid/test-install/pike/7.5.1/bin/pike)
Might be machine code?
/ Mirar
Previous text:
2002-12-11 23:05: Subject: gcc 3.2
But then you better use --without-machine-code too, since valgrind gets very confused when machine code is overwritten.
/ Martin Stjernholm, Roxen IS