Custom Query (80 matches)

It is now impossible to run Openfire(Java) with Odin 0.8.1 Severel different crashes - see Java ticket 133 (and 146)

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

rwalsh: I consider *every* message that the compiler generates to be a problem. If nothing else, having thousands of "harmless" messages makes it nearly impossible to find and fix the few that are actually telling you something important.

Eliminating all these messages is unbelievably boring & time- consuming, but essential, IMHO. So far, I've eliminated nearly all messages when compiling these directories:

advapi32, crypt32, kernel32, ntdll, user32, and winmm

There are two info messages that can't be eliminated because of the odd way that debug printf()'s are turned off (i.e. "the condition is always TRUE" & "the condition is always FALSE"). For these, I'm just using sed to filter them from the output:

nmake 2>&1 | sed -u /EDC042[45]/D | tee build.log