[ODEJava] CarTerrainExample & OS X = JVM crash

Game Mechanics
#1

No matter whether I use JRE 1.4.2 or 1.5.0… My odejava components are latest releases (2004-10-30).

OS X 10.4.2

And here is the crashlog (partly):

Date/Time: 2005-07-24 15:47:31.361 +0200
OS Version: 10.4.2 (Build 8C46)
Report Version: 3

Command: java
Path: /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/bin/java
Parent: java [444]

Version: ??? (???)

PID: 8831
Thread: 1

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0xf0003ff0

Thread 0:
0 libSystem.B.dylib 0x9000a778 mach_msg_trap + 8
1 libSystem.B.dylib 0x9000a6bc mach_msg + 60
2 com.apple.CoreFoundation 0x9074b3d8 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x9074acdc CFRunLoopRunSpecific + 268
4 com.apple.HIToolbox 0x93123be0 RunCurrentEventLoopInMode + 264
5 com.apple.HIToolbox 0x93123274 ReceiveNextEventCommon + 380
6 com.apple.HIToolbox 0x931230e0 BlockUntilNextEventMatchingListInMode + 96
7 com.apple.AppKit 0x9361e1a4 _DPSNextEvent + 384
8 com.apple.AppKit 0x9361de68 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
9 com.apple.AppKit 0x9361a3cc -[NSApplication run] + 472
10 libawt.jnilib 0x9b384ce4 +[AWTStarter startAWT:] + 364
11 com.apple.Foundation 0x9288a760 __NSFireMainThreadPerform + 276
12 com.apple.CoreFoundation 0x9077c1a8 __CFRunLoopPerformPerform + 104
13 com.apple.CoreFoundation 0x9074bd2c __CFRunLoopDoSources0 + 384
14 com.apple.CoreFoundation 0x9074b25c __CFRunLoopRun + 452
15 com.apple.CoreFoundation 0x9074acdc CFRunLoopRunSpecific + 268
16 java 0x00005194 0x1000 + 16788
17 java 0x0000232c 0x1000 + 4908
18 java 0x000021cc 0x1000 + 4556

Thread 1 Crashed:
0 libode.dylib 0x09d4cac4 dxHashSpace::collide(void*, void ()(void, dxGeom*, dxGeom*)) + 636 (icplusplus.c:27)
1 libodejava.jnilib 0x0178ce48 Java_org_odejava_collision_JavaCollision_spaceCollide + 60 (icplusplus.c:27)
2 <<00000000>> 0x03f38580 0 + 66291072
3 <<00000000>> 0x03f31ef0 0 + 66264816
4 <<00000000>> 0x03f31fb0 0 + 66265008
5 <<00000000>> 0x03f31fb0 0 + 66265008
6 <<00000000>> 0x03f31fb0 0 + 66265008
7 <<00000000>> 0x03f2f16c 0 + 66253164
8 libclient.dylib 0x963dcb1c jio_snprintf + 295304
9 libclient.dylib 0x963dc9c4 jio_snprintf + 294960
10 libclient.dylib 0x963f98c8 JVM_MaxMemory + 4300
11 libclient.dylib 0x9646a908 JVM_SupportsCX8 + 2608
12 java 0x00003100 0x1000 + 8448
13 java 0x00005034 0x1000 + 16436
14 libSystem.B.dylib 0x9002c3d4 _pthread_body + 96

Model: PowerBook6,8, BootROM 4.9.0f0, 1 processors, PowerPC G4 (1.2), 1.5 GHz, 768 MB
Graphics: GeForce FX Go5200, GeForce FX Go5200, AGP, 64 MB

#2

It’s probably an odejava problem - so: have you tried the newest odejava from cvs?

#3

Talking of odejava problems : i think there are a lot of Odejava problems… That aren’t in ODE.
I read that the JME team has fixed a lot of bugs for the JME Physic Engine. Could it be possible to merge their bug fixes into the main Odejava CVS ?
Example problems :

  • Why Odejava do crashes with large trimeshs ?
  • Why Odejava sometimes (still) don’t detect collisions on trimeshes ?
  • Why if you have e.g. a table model with a trimesh it won’t keep stable correctly ?
#4

Apparently the jME physics group were going to submit patches to Odejava for stuff they’ve changed. From what I understand they basically have a modified version of Odejava featuring close integration with jME.

It would be very nice to see these patches :slight_smile:

Will.

#5

I agree :slight_smile:

#6

Some update…

I managed to get things running by getting latest from CVS and building myself. :smiley: Maybe it would be a good idea to update those files on the web page, too.

Pepez