--- Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Good. So you can step through the JIT code.
>
Yes and no. On Monday, arithmetics_26 was not
coredumping parrot under JIT that I can remember. It
is now, but I am able to debug/trace with JIT. I am
not sure what to do since comparing the trace to the
JIT trace shows both print ok for all 4 tests, the JIT
version just coredumps after.
REGULAR TRACE
128 eq I2, I7, 6 - I2=5, I7=5,
134 print "ok 4\n"
ok 4
PC=136; OP=<err>
JIT TRACE
47 eq I2, I7, OK4
(gdb) n
50 OK4: print "ok 4\n"
(gdb) n
ok 4
Program received signal SIGSEGV, Segmentation fault.
0x102a3901 in ?? ()
trans_9 does not coredump, it just says the test is
not ok. I can't however debug/trace it with JIT.
This means I can't see where things go wrong:
$ parrot -o trans_9.pbc -d trans_9.pasm
$ gdb parrot
GNU gdb 2003-09-20-cvs (cygwin-special)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General
Public License, and you are
welcome to change it and/or distribute copies of it
under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) b runops_jit
Breakpoint 1 at 0x466bf6: file src/interpreter.c, line
548.
(gdb) r -d -j trans_9.pbc
Starting program: /perl/parrot/parrot.exe -d -j
trans_9.pbc
Program received signal SIGSEGV, Segmentation fault.
0x77e75a3d in KERNEL32!IsBadWritePtr () from
/cygdrive/c/WINDOWS/system32/kernel32.dll
(gdb) continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x77e75a3f in KERNEL32!IsBadWritePtr () from
/cygdrive/c/WINDOWS/system32/kernel32.dll
(gdb) continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x77e75a3d in KERNEL32!IsBadWritePtr () from
/cygdrive/c/WINDOWS/system32/kernel32.dll
(gdb) continue
Continuing.
*** Parrot VM: Setting stack top. ***
*** Parrot VM: JIT core ***
*** Parrot VM: Setting up ARGV array in P5. Current
argc: 1 ***
0: trans_9.pbc
Breakpoint 1, runops_jit (interpreter=0x100d1d80,
pc=0x3f00e0) at src/interpreter.c:548
548 jit_f jit_code = (jit_f)
D2FPTR(init_jit(interpreter, pc));
(gdb) n
Program received signal SIGSEGV, Segmentation fault.
0x00522808 in Parrot_jit_debug_stabs
(interpreter=0x100d1d80) at src/jit_debug.c:348
348 fprintf(stabs, ".stabn " N_SLINE
",0,%d,%d /* %s */\n", line,
(gdb)
WRT arithmetics_26 that coredumps, but I can
debug/trace with JIT - what should I look for?
WRT trans_9-12,17,18 that does not coredump and I
can't debug/trace with JIT - what should I do next?
Cheers
Joshua Gatcomb
a.k.a. Limbic~Region
__________________________________
Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2'
http://movies.yahoo.com/showtimes/movie?mid=1808405861
