was bug 1264043 in 1.0.2 days. It was filed on sqe and closed. Appears to be a jvm x86 bug.

segfaults equally well with the jit.

The java thread dump and the messed up dbx core trace follow


# java javasoft.sqe.tests.vm.idiv.idiv002.idiv00201.idiv00201
SIGFPE 8* arithmetic exception
    si_signo [8]: SIGFPE 8* arithmetic exception
    si_errno [0]: Error 0
    si_code [1]: FPE_INTOVF [addr: 0xdffd3139]

        stackbase=8047A6C, stackpointer=8047974

Full thread dump:
    "Finalizer thread" (TID:0xdef00220, sys_thread_t:0xdeb14da8, state:R) prio=1
    "Async Garbage Collector" (TID:0xdef001d8, sys_thread_t:0xdeb36da8, state:R) prio=1
    "Idle thread" (TID:0xdef00190, sys_thread_t:0xdeb58da8, state:R) prio=0
    "Clock" (TID:0xdef000d0, sys_thread_t:0xdeb7ada8, state:CW) prio=12
    "main" (TID:0xdef000a8, sys_thread_t:0x808f520, state:R) prio=5 *current thread*
        javasoft.sqe.tests.vm.idiv.idiv002.idiv00201.idiv00201.run(idiv00201.jasm)
        javasoft.sqe.tests.vm.idiv.idiv002.idiv00201.idiv00201.main(idiv00201.jasm)
Monitor Cache Dump:
Registered Monitor Dump:
    Thread queue lock: <unowned>
    Name and type hash table lock: <unowned>
    String intern lock: <unowned>
    JNI pinning lock: <unowned>
    JNI global reference lock: <unowned>
    BinClass lock: <unowned>
    Class loading lock: <unowned>
    Java stack lock: <unowned>
    Code rewrite lock: <unowned>
    Heap lock: <unowned>
    Has finalization queue lock: <unowned>
    Finalize me queue lock: <unowned>
    Monitor IO lock: <unowned>
    Child death monitor: <unowned>
    Event monitor: <unowned>
    I/O monitor: <unowned>
    Alarm monitor: <unowned>
        Waiting to be notified:
            "Clock"
    Sbrk lock: <unowned>
    Monitor cache expansion lock: <unowned>
    Monitor registry: owner "main" (0x808f520, 1 entry)
Thread Alarm Q:
Abort - core dumped

dbx: core file read error: address 0x30031 not in data space
dbx: attempt to read stack failed - bad frame pointer
(/ws/on297-tools/SUNWspro/SC4.2/bin/dbx) where
=>[1] _lwp_kill(), at 0xdfe2fa7f
  [2] sysAbort(0x6, 0x0), at 0xdffcbe91
  [3] signalHandlerPanic(0x8, 0x8000000), at 0xdffcd5a6
  ---- called from signal handler with signal 8 (SIGFPE) ------
  [4] N2_idiv5(), at 0xdffd3139
  [5] do_execute_java_method_vararg(0x80000000, 0x90800000), at 0xdffb46ad
  [6] 0xdef007e8(0x0, 0xb8000000), at 0xdef007e7
  [7] 0x2(0x0, 0x0), at 0x1
  [8] 0xb28a9(0xdef334d8, 0xe0def334), at 0xb28a8
  [9] 0x80759e0(0x80917c0, 0x68080917), at 0x80759df

bren.caperon@Eng 1997-03-05

I had originally thought this was the same failure as in lang/conv08304 that problem has been fixed and the tests is now passing.

Note: I had also thought the following tests were the same bug but may not be:

vm/instr/irem/irem001/irem00101/irem00101.html Failed. unexpected exit code
vm/instr/irem/irem006/irem00601/irem00601.html Failed. unexpected exit code
vm/instr/ret/ret001/ret00101/ret00101.html Failed. unexpected exit code

stack trace is the same for the following failures

lang/EXPR/expr274/expr27401/expr27401.html
lang/EXPR/expr275/expr27501/expr27501.html