>
> 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 -
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 c
[EMAIL PROTECTED] wrote:
I am using Kaffe for a research project in school where I am adding a
bytecode to some .class files. It's a new bytecode and I'm trying to
make the changes to the JIT to account for the new bytecode, but coming
across some trouble.
I started out making changes to the in
I am using Kaffe for a research project in school where I am adding a
bytecode to some .class files. It's a new bytecode and I'm trying to
make the changes to the JIT to account for the new bytecode, but coming
across some trouble.
I started out making changes to the interpreter. Mostly, it inv
