Re: [kaffe] bytecodes
Hi, I'm working on trace's output with MOREJIT option and I would like to print some values of stack and local variables array. Is there some function that returns this? In practice, I would like to see the value used from array when the instruction aload 0 is executed. Thanks, Eduardo Melione On Wed, 7 Jan 2004, Dalibor Topic wrote: Hi Eduardo, Eduardo Melione Abreu wrote: Thank you! I want to know the values of the most simple bytecodes, whose operate on local integer variables, stack and constants (all about 65 bytecodes). However, I have interes to do this patch. What I have do do? How and where do I start? I'm very interested about... Actually, there is also the vmdebug option MORE_JIT, that gives you some slightly better output: @0: aload 0 @1: iload 1 @2: iconst 0 @3: invokevirtual 173 vs 000: ALOAD_0 000: ALOAD_1 000: ALOAD_2 000: ALOAD_3 001: GETFIELD 004: IFNE 007: ILOAD_1 007: ILOAD_2 007: ILOAD_3 008: ALOAD_0 008: ALOAD_1 008: ALOAD_2 008: ALOAD_3 009: GETFIELD 012: ARRAYLENGTH with INT_INSTR. It would be great if you could take the MORE_JIT output, and extend it to resolve the constants, for example, and print its arguments. the function is called trace_jcode in kaffe/kaffevm/kaffe.def. Take a look at the bytecodes that interest you, and add better humanely readable output to their trace_jcode calls. Don't hesitate to ask questions. ;) cheers, dalibor topic ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
Re: [kaffe] bytecodes
Hi Dalibor, I downloaded kaffe version 1.1.3 and I've tried to use the MOREJIT option so it is giving a looping whit the bytecodes and its arguments at standart output. Also, the instructions do not seems to be the same that I have compiled. I am not the root user... What can be wrong? Tanks Eduardo. On Wed, 7 Jan 2004, Dalibor Topic wrote: Hi Eduardo, Eduardo Melione Abreu wrote: Thank you! I want to know the values of the most simple bytecodes, whose operate on local integer variables, stack and constants (all about 65 bytecodes). However, I have interes to do this patch. What I have do do? How and where do I start? I'm very interested about... Actually, there is also the vmdebug option MORE_JIT, that gives you some slightly better output: @0: aload 0 @1: iload 1 @2: iconst 0 @3: invokevirtual 173 vs 000: ALOAD_0 000: ALOAD_1 000: ALOAD_2 000: ALOAD_3 001: GETFIELD 004: IFNE 007: ILOAD_1 007: ILOAD_2 007: ILOAD_3 008: ALOAD_0 008: ALOAD_1 008: ALOAD_2 008: ALOAD_3 009: GETFIELD 012: ARRAYLENGTH with INT_INSTR. It would be great if you could take the MORE_JIT output, and extend it to resolve the constants, for example, and print its arguments. the function is called trace_jcode in kaffe/kaffevm/kaffe.def. Take a look at the bytecodes that interest you, and add better humanely readable output to their trace_jcode calls. Don't hesitate to ask questions. ;) cheers, dalibor topic ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
[kaffe] bytecodes
Hi, I would like to have a log file indicating those bytecodes that the virtual machine really executed, and its arguments if possible. Where and how I can get this information at Kaffe? Thanks, Eduardo Melione. ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
Re: [kaffe] bytecodes
Hi Eduardo, Eduardo Melione Abreu wrote: Hi, I would like to have a log file indicating those bytecodes that the virtual machine really executed, and its arguments if possible. Configure and build kaffe with the interpreter engine (--with-engine=intrp) and debugging enabled (--enable-debug). Then you can use kaffe -vmdebug INT_INSTR YourClass to see all the executed bytecodes. It doesn't show the arguments, though. It would be great if you could write a patch for that functionality, if you are not tainted, i.e. have looked at Sun's sources, decompiled them, etc. cheers, dalibor topic ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
Re: [kaffe] bytecodes
Thank you! I want to know the values of the most simple bytecodes, whose operate on local integer variables, stack and constants (all about 65 bytecodes). However, I have interes to do this patch. What I have do do? How and where do I start? I'm very interested about... Eduardo. On Wed, 7 Jan 2004, Dalibor Topic wrote: Hi Eduardo, Eduardo Melione Abreu wrote: Hi, I would like to have a log file indicating those bytecodes that the virtual machine really executed, and its arguments if possible. Configure and build kaffe with the interpreter engine (--with-engine=intrp) and debugging enabled (--enable-debug). Then you can use kaffe -vmdebug INT_INSTR YourClass to see all the executed bytecodes. It doesn't show the arguments, though. It would be great if you could write a patch for that functionality, if you are not tainted, i.e. have looked at Sun's sources, decompiled them, etc. cheers, dalibor topic ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
Re: [kaffe] bytecodes
Hi Eduardo, Eduardo Melione Abreu wrote: Thank you! I want to know the values of the most simple bytecodes, whose operate on local integer variables, stack and constants (all about 65 bytecodes). However, I have interes to do this patch. What I have do do? How and where do I start? I'm very interested about... Actually, there is also the vmdebug option MORE_JIT, that gives you some slightly better output: @0: aload 0 @1: iload 1 @2: iconst 0 @3: invokevirtual 173 vs 000: ALOAD_0 000: ALOAD_1 000: ALOAD_2 000: ALOAD_3 001: GETFIELD 004: IFNE 007: ILOAD_1 007: ILOAD_2 007: ILOAD_3 008: ALOAD_0 008: ALOAD_1 008: ALOAD_2 008: ALOAD_3 009: GETFIELD 012: ARRAYLENGTH with INT_INSTR. It would be great if you could take the MORE_JIT output, and extend it to resolve the constants, for example, and print its arguments. the function is called trace_jcode in kaffe/kaffevm/kaffe.def. Take a look at the bytecodes that interest you, and add better humanely readable output to their trace_jcode calls. Don't hesitate to ask questions. ;) cheers, dalibor topic ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
