Hi, <[EMAIL PROTECTED]> wrote: ><[EMAIL PROTECTED]> wrote: >> Well, actually I can step inside kaffe.def from the function >> runVirtualMachine. But it just says "in kaffe.def: line n" without showing >> the C code that's getting executed. So that's what I meant in my earlier >> mail. Are you getting the same problem? >That is what I get.
I have experienced this several times. And I believe it can be called a bug of gdb, but fixing it should need extra effort, and I modify {intrp,jit,jit3}/machine.c to include the contents of 'kaffe.def' where originally 'include' statement exists. At least I can see which line is executed by doing this. If I have to report some problem caused by original kaffe.def, then I need to do some calculation but it should be easier to see the inside of gdb ;-) Kiyo _______________________________________________ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe