Status fields:
creation_ts: | 2007-09-11 02:12 |
---|---|
component: | unspecified |
version: | default branch |
rep_platform: | arm |
op_sys: | Linux |
bug_status: | RESOLVED |
resolution: | DUPLICATE |
reporter: | michi@complang.tuwien.ac.at |
During Jetty-6.1.1 startup the following error message is printed. The given instruction is a valid ARM instruction and should not raise an SIGILL. I suspect a cacheflushing problem since the given instruction is at a very likely patch position. [michi:/nfs/scratch/michi/testing/jetty-6.1.1:504] cacao -jar start.jar 2007-09-11 02:07:47.406::INFO: Logging to STDERR via org.mortbay.log.StdErrLog 2007-09-11 02:08:00.643::INFO: jetty-6.1.1 2007-09-11 02:08:04.383::INFO: Deploy /nfs/scratch/michi/testing/jetty- 6.1.1/contexts/javadoc.xml -> org.mortbay.jetty.servlet.Context@1293ed8{/javadoc,file:/nfs/scratch/michi/testing/jetty - 6.1.1/javadoc/} 2007-09-11 02:08:06.621::INFO: Deploy /nfs/scratch/michi/testing/jetty-6.1.1/contexts/test.xml - > org.mortbay.jetty.webapp.WebAppContext@17ac30{/test,/nfs/scratch/michi/testing/jetty- 6.1.1/webapps/test} 2007-09-11 02:08:35.565::WARN: Unknown realm: Test JAAS Realm LOG: [0x0002c00c] md_signal_handler_sigill: unknown illegal instruction: inst=e590b000 0x40cf9820: e590b000 ldr fp, [r0] cacao: ../../../../../../src/vm/jit/arm/linux/md-os.c:177: md_signal_handler_sigill: Assertion `0' failed. Aborted
Probably generated by instruction: //in class definition protected final static Object pusherMutex = new Object(); //in function synchronized (pusherMutex) { ... }
Why do you think that? Does this break for you?
(In reply to comment #2) > Why do you think that? Does this break for you? I got this error first time after I added some code including this (rest of code is nothing special).
Could you attach the whole testcase? I could not reproduce it with this snippet.
*** This bug has been marked as a duplicate of bug 85 ***