BZ #134: Alignment trap

Status fields:

I was running Concierge 1.0.0 on Cacao 0.99.4 with classpath 0.98 on an arm, and I got
an alignment trap.
I built Cacao with the Open Embedded environment.

Concierge args were
-Dch.ethz.iks.concierge.jars=file:./bundles

-Dch.ethz.iks.concierge.log.enabled=true

-Dch.ethz.iks.concierge.log.level=4



-init



-istart event-admin-1.0.0.jar

-istart service-tracker-1.0.0.jar

The log looks like :
Alignment trap: java (2353) PC=0x401e9944 Instr=0xe5126004 Address=0xbee555b5 FSR 0x001
LOG: [0x4001d540] We received a SIGSEGV and tried to handle it, but we were
Alignment trap: java (2353) PC=0x401ec498 Instr=0xe5912000 Address=0x00006f73 FSR 0x001
Alignment trap: java (2353) PC=0x401e9894 Instr=0xe591e008 Address=0x00000116 FSR 0x001
Alignment trap: java (2353) PC=0x401e9944 Instr=0xe5126004 Address=0xbee54d5d FSR 0x001
Alignment trap: java (2353) PC=0x401ec498 Instr=0xe5912000 Address=0x00006f73 FSR 0x001
LOG: [0x4001d540] unable to find a Java method at:
LOG: [0x4001d540]
LOG: [0x4001d540] PC=0x401e9888
LOG: [0x4001d540]
LOG: [0x4001d540] Dumping the current stacktrace:
LOG: [0x4001d540] We received a SIGSEGV and tried to handle it, but we were
LOG: [0x4001d540] unable to find a Java method at:
LOG: [0x4001d540]
LOG: [0x4001d540] PC=0x401e9894
LOG: [0x4001d540]
LOG: [0x4001d540] Dumping the current stacktrace:
LOG: [0x4001d540] We received a SIGSEGV and tried to handle it, but we were
LOG: [0x4001d540] unable to find a Java method at:
LOG: [0x4001d540]
LOG: [0x4001d540] PC=0x401ec498
LOG: [0x4001d540]
LOG: [0x4001d540] Dumping the current stacktrace:
LOG: [0x4001d540] We received a SIGSEGV and tried to handle it, but we were
LOG: [0x4001d540] unable to find a Java method at:
LOG: [0x4001d540]
LOG: [0x4001d540] PC=0x401ec498

I will try to reproduce the problem on one of our boards. Stay tuned.

Cannot reproduce with a current CACAO, works fine on my SheevaPlug.

I just wanted to try if I can reproduce it with 0.99.4, but that segfaults immediately
for me, with an inconclusive stack trace, so I'll just leave it at that.