BZ #104: assertion in descriptor_params_from_paramtypes

Status fields:

creation_ts:2008-09-10 17:56
component:vm
version:default branch
rep_platform:All
op_sys:All
bug_status:RESOLVED
resolution:DUPLICATE
reporter:twisti@complang.tuwien.ac.at
I was viewing a PDF file with PDFRenderer, pressed page-down and I got this assertion:

$ java -jar PDFRenderer.jar EW_2008.pdf
java: ../../../src/vm/descriptor.c:1063: descriptor_params_from_paramtypes: Assertion
`thisclass' failed.
Aborted (core dumped)

Here is the backtrace:

(gdb) where
#0  0x00002ac6f4383ef5 in raise () from /lib/libc.so.6
#1  0x00002ac6f4385413 in abort () from /lib/libc.so.6
#2  0x00002ac6f437cdc9 in __assert_fail () from /lib/libc.so.6
#3  0x00002ac6f46f436b in descriptor_params_from_paramtypes (md=0x2aaaad105e78,
mflags=0) at ../../../src/vm/descriptor.c:1063
#4  0x00002ac6f4724da6 in parse (jd=0x1063490) at ../../../../src/vm/jit/parse.c:1244
#5  0x00002ac6f471e76a in jit_compile_intern (jd=0x1063490) at
../../../../src/vm/jit/jit.cpp:630
#6  0x00002ac6f471f298 in jit_compile (m=0x2aaaad104e10) at
../../../../src/vm/jit/jit.cpp:384
#7  0x00002ac6f471f354 in jit_compile_handle (m=0x2aaaad104e10, pv=0x2aaaabd54130,
ra=0x2aaaabd54166, mptr=0x2aaaad110d80)
    at ../../../../src/vm/jit/jit.cpp:1043
#8  0x00002ac6f474643e in trap_handle (type=9, val=46912536382848, pv=0x0,
sp=0x401eddd0, ra=0x2aaaabd54166, xpc=0x2aaaabd54163,
    context=0x401ed980) at ../../../../src/vm/jit/trap.c:183
#9  0x00002ac6f477a073 in md_signal_handler_sigsegv (sig=11, siginfo=0x401edab0,
_p=0x401ed980)
    at ../../../../../../src/vm/jit/x86_64/linux/md-os.c:184
#10 <signal handler called>

I cannot reproduce the assertion.

Comment #1 by twisti@complang.tuwien.ac.at on 2008-09-10 17:57:10

Is this line OK?

http://mips.complang.tuwien.ac.at/hg/cacao/annotate/a086e6f36648/src/vm/descriptor.c#l10
62

Comment #2 by twisti@complang.tuwien.ac.at on 2008-09-10 17:57:51

Edwin, can you tell me if the above line is OK?

Comment #3 by stefan@complang.tuwien.ac.at on 2011-12-05 23:31:25

*** This bug has been marked as a duplicate of bug 163 ***