[kaffe] debugging JITted methods
stack at cs.utah.edu
Fri Mar 19 08:17:02 PST 2004
> Dalibor Topic wrote:
> > See the xdebugging support (FAQ.xdebugging) for a way to generate
> > debugging information in jitted code siutable for gdb.
> > You can take a look at the emitted code from the jitter by configuring
> > and building kaffe with --enable-debug and using kaffe -vmdebug JIT to
> > run your classes.
> I had tried a bit of this before, but it seems that I finally got the
> right combination of things. Good grief, 60,000 lines of asm for hello
The test/internal directory runs tests on small, simplistic methods to
help you get started. Note that you need to have jikes available for this
to be activated.
> >> I expect implementing the new code could be done really cleanly (and
> >> quickly) by someone who really understands how the JIT is
> >> implemented. I'm just having a tough time figuring that out.
> > See FAQ.jit3 for a nice overview of how jit3 works.
> It's my understanding that there is no JIT3 for Alpha. Is that the case?
> I definately need to stick with Alpha at this point. I found a pretty
> good summary of the JIT process, though, which helped clear things up some.
Yeah, jit1 and jit3 are roughly the same.
More information about the kaffe