Opened 8 years ago

Closed 8 years ago

#65 closed defect (invalid)

Jeti/2 can't start anymore with new GCC builds

Reported by: yoda Owned by:
Priority: Feedback Pending Milestone: general enhancement
Component: odin Version: 0.8.x
Severity: medium Keywords:
Cc:

Description

Trying to start Jeti/2 (using Java6) crashes persistently during startup.

12-31-2011 01:04:02 SYS3170 PID 0079 TID 001c Slot 0096 L:\JAVA6\BIN\JAVA.EXE 00000000 00000000 EAX=00000000 EBX=00000000 ECX=08edf0ec EDX=2215bbe0 ESI=08edf0b0 EDI=1a618950 DS=0053 DSACC=d0f3 DSLIM=4fffffff ES=0053 ESACC=d0f3 ESLIM=4fffffff FS=4667 FSACC=00f3 FSLIM=00000fff GS=0000 GSACC= GSLIM= CS:EIP=005b:1d326020 CSACC=d0df CSLIM=4fffffff SS:ESP=0053:08edf010 SSACC=d0f3 SSLIM=4fffffff EBP=08edf048 FLG=00010246

# # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x1cd00d3f, pid=121, tid=7929884 # # JRE version: 6.0-b22 # Java VM: OpenJDK Client VM (19.0-b09 mixed mode os2-x86 ) # Problematic frame: # C [IPHLPAPI+0xd3f] # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #


Current thread (0x225b7800): JavaThread? "Thread-9" [_thread_in_native, id=7929884, stack(0x08de0000,0x08ef0000)]

siginfo: ExceptionCode?=0xc0000005, writing address 0x32342e35

Registers: EAX=0x000002f8, EBX=0x00b8d340, ECX=0x00000370, EDX=0x32342e35 ESP=0x08edeab0, EBP=0x08edeae8, ESI=0x225c52c0, EDI=0x00000280 EIP=0x1cd00d3f, EFLAGS=0x00010202

Register to memory mapping:

EAX=0x000002f8 0x000002f8 is pointing to unknown location

EBX=0x00b8d340 0x00b8d340 is pointing to unknown location

ECX=0x00000370 0x00000370 is pointing to unknown location

EDX=0x32342e35 0x32342e35 is an unallocated location in the heap

ESP=0x08edeab0 0x08edeab0 is pointing into the stack for thread: 0x225b7800 "Thread-9" prio=6 tid=0x225b7800 nid=0x79001c runnable [0x08ede000]

java.lang.Thread.State: RUNNABLE

EBP=0x08edeae8 0x08edeae8 is pointing into the stack for thread: 0x225b7800 "Thread-9" prio=6 tid=0x225b7800 nid=0x79001c runnable [0x08ede000]

java.lang.Thread.State: RUNNABLE

ESI=0x225c52c0 0x225c52c0 is pointing to unknown location

EDI=0x00000280 0x00000280 is pointing to unknown location

Top of Stack: (sp=0x08edeab0) 0x08edeab0: 00000000 00000000 00000000 00000000 0x08edeac0: 1ffc5e51 00000041 08edeb50 00000002 0x08edead0: 08edeb10 08edeae4 00000000 08edeb10 0x08edeae0: 08edeafc 08edeb50 08edeb28 1f4a92a4 0x08edeaf0: 00000041 08edeb50 00000002 08edeb10 0x08edeb00: 1ffc5e51 00000041 08edeb90 00000002 0x08edeb10: 00000002 08ed027f 00004667 00000002 0x08edeb20: 00000041 1a618950 08edef68 1f4d4cf4

Instructions: (pc=0x1cd00d3f) 0x1cd00d2f: 75 f7 89 da 81 c2 d4 01 00 00 74 0a 90 83 c0 28 0x1cd00d3f: 8b 12 85 d2 75 f7 89 da 81 c2 fc 01 00 00 74 0a

Stack: [0x08de0000,0x08ef0000], sp=0x08edeab0, free space=1018k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [IPHLPAPI+0xd3f]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j 0x23179fa5

Attachments (1)

Crash179.zip (1.6 KB) - added by yoda 8 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 8 years ago by yoda

Tested with version 0.8.2

comment:2 Changed 8 years ago by guzzi

Odin 0.8.2, java 1.6.0 build 22, jeti/2 0.7.8 build 4 runs fine here

comment:3 Changed 8 years ago by yoda

  • Version set to 0.8.x

Interesting.

I tested exactly same Jeti and Odin on another eCS (2.1GA) partition, and yes, there it starts without that error.

On my other partition, it fails on every start, since new Odin was installed.

After having tried many times, things changed a bit, now I get:

LIBC Error: Couldn't register process in shared memory!

and:

01-19-2012 03:03:56 SYS3175 PID 00ad TID 0001 Slot 0088 L:\JAVA6\BIN\JAVA.EXE c0000005 1f44c5aa P1=00000001 P2=00000006 P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=0000f683 ECX=0081fd60 EDX=1ab50000 ESI=0000150b EDI=00000000 DS=0053 DSACC=d0f3 DSLIM=4fffffff ES=0053 ESACC=d0f3 ESLIM=4fffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC= GSLIM= CS:EIP=005b:1f44c5aa CSACC=d0df CSLIM=4fffffff SS:ESP=0053:0081fdb4 SSACC=d0f3 SSLIM=4fffffff EBP=0081fdcc FLG=00010206

WGSS50.DLL 0001:0000c5aa

comment:4 Changed 8 years ago by dmik

  • Resolution set to wontfix
  • Status changed from new to closed

I cannot confirm your problem on my system.

"LIBC Error: Couldn't register process in shared memory!" suggests us that you have an incompatible mixture of LIBC DLLs on your system. LIBC063 and LIBC064(x) interfere with each other in the shared memory and may show various types of strange behavior including crashes exactly like the above.

So please clean up your environment on the second machine and it should work then.

comment:5 Changed 8 years ago by yoda

  • Milestone changed from 0.8.3 to general enhancement
  • Resolution wontfix deleted
  • Status changed from closed to reopened

The WGSS50.DLL might have been due to the LIBC problems. LIBC have now been updated to the newest, including the fix version. I'm now back to the same crash as initially - which happens on every start of Jeti/2 . The crash does BTW seem identical to one of the crashes I get in OpenFire? with the new GCC builds. This is on 2 completely different machines.

Changed 8 years ago by yoda

comment:6 Changed 8 years ago by dmik

  • Priority changed from critical to Feedback Pending
  • Severity changed from highest to medium

Please check the new builds of Odin 0.8.4 and OpenJDK b24 GA2.

I can repeat again, that the problem doesn't show up here.

comment:7 Changed 8 years ago by dmik

  • Resolution set to invalid
  • Status changed from reopened to closed

And in either case, this is not the right place for the defect. There is http://svn.netlabs.org/java/ticket/133, please continue there (or create a new Java ticket).

Note: See TracTickets for help on using tickets.