On Wed, 2005-09-21 at 11:44 +0100, Jonathan Worthington wrote: > >> but I can cause a segfault from random input on x86. > >> > >> -- > >> $ ./parrot -j docs/running.pod > >> Segmentation fault
> This is a Bad Thing and needs fixing. I'll see what I can find - I don't > even see a segfault or any other error mesage under Win32, which is at least > as bad. It segfaults on me in Linux. The problem is that the JIT core always expects there to be valid op_start and op_end members in interpreter->code, so when there's no code there, it blindly dereferences them. I don't have time now to trace what the other runcores do in that situation, but I put a couple of guards in src/interpreter.c in init_jit() and caused different errors. -- c
