Opened 10 years ago
Closed 8 years ago
#18 closed defect (fixed)
JavaByteCodeDeassembler does not disassemble all Java methods
| Reported by: | Jan Vraný | Owned by: | hlopkmar |
|---|---|---|---|
| Priority: | major | Milestone: | milestone: |
| Component: | stx:libjava | Keywords: | |
| Cc: |
Description
JavaByteCodeDeassembler does not disassemble all Java methods loaded during
VM boot. Execute
JavaByteCodeDeassemblerTests new diassembleAll
the fails collection contains all Java methods in the running
system that failed to be disassembled (meaning that an error occurred during
disassembling, not that they are disassembled correctly :-)
Change History (3)
comment:1 Changed 10 years ago by
| Status: | new → accepted |
|---|
comment:3 Changed 8 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
Note: See
TracTickets for help on using
tickets.
Short report:
We have only two remaining bugs, the first one depends on ticket #19 (multibyte chars), the second problem is funnier and I'm writing it here so maybe somebody will know more about the issue.
During the test, java method on a java class is disassembled. Some classes are funny - they're missing constant pool (cp is nil), but when you retrieve the same class using Java classForName:, the constant pool is there. I'll dig deeper tomorrow.