Dear all,
I'm writing in this section for an issue that I believe could be classified as a bug. I'm quite new of Irrlicht, but it looks like the problem I'm experiencing is not related to my code.
I'm a Mac user and I started to use Irrlicht few weeks ago. Following the official tutorials, I've been able to write and run many different applications using the computer I have at work (Mac Pro 2.8GHz quad-core, Mac OS X 10.5.5, Irrlicht 1.4.2, g++, ATI Radeon HD 2600 - 256MB RAM). The same applications compile and run smoothly on a MacBook Pro with the identical software configuration (the only meaningful difference is the graphic card, that in this case is an ATI Mobility Radeon X1600 PCI Express x16 - 256 MB RAM).
The problem arises when I try to run the same applications on my personal laptop, which is a MacBook Air. On this computer (again, same identical software configuration), the applications compile correctly but they immediately crash at run-time. Consider that the MacBook Air (which doesn't belong to the latest generation, released few days ago) doesn't have a dedicated graphics card. It uses in fact the Intel GMA X3100 chipset.
I post here the first part of a crash report generated by MacOS after running one of the above mentioned applications. The error is generated by the createDevice function (in this case invoked as: device = irr::createDevice(video::EDT_SOFTWARE, dimension2d<s32>(1024, 768), 16, false, false, false, 0)). I've tried both using OPENGL and SOFTWARE options, but the outcome is always the same.
Process: MAVs3D [1493]
Path: /Users/fabioruini/Desktop/MAVs_3d/MAVs3D.app/Contents/MacOS/MAVs3D
Identifier: MAVs3D
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [65]
Date/Time: 2008-10-28 21:43:31.147 +0000
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 MAVs3D 0x00209baa irr::CIrrDeviceMacOSX::setResize(int, int) + 58
1 com.apple.Foundation 0x902b81da _nsnote_callback + 106
2 com.apple.CoreFoundation 0x9018baba __CFXNotificationPost + 362
3 com.apple.CoreFoundation 0x9018bd93 _CFXNotificationPostNotification + 179
4 com.apple.Foundation 0x902b5440 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
5 com.apple.Foundation 0x902bec88 -[NSNotificationCenter postNotificationName:object:] + 56
6 com.apple.AppKit 0x945ad13c -[NSWindow _setFrameCommon:display:stashSize:] + 1794
7 com.apple.AppKit 0x945aca32 -[NSWindow setFrame:display:] + 78
8 com.apple.AppKit 0x945b6034 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 783
9 com.apple.AppKit 0x945b5cc8 -[NSWindow orderWindow:relativeTo:] + 105
10 com.apple.AppKit 0x9457d65a -[NSWindow makeKeyAndOrderFront:] + 189
11 MAVs3D 0x002098fe irr::CIrrDeviceMacOSX::createWindow(irr::core::dimension2d<int> const&, unsigned int, bool, bool, bool) + 638
12 MAVs3D 0x0020ba36 irr::CIrrDeviceMacOSX::CIrrDeviceMacOSX(irr::video::E_DRIVER_TYPE, irr::core::dimension2d<int> const&, unsigned int, bool, bool, bool, bool, irr::IEventReceiver*, char const*) + 694
13 MAVs3D 0x0020bc33 irr::createDeviceEx(irr::SIrrlichtCreationParameters const&) + 99
14 MAVs3D 0x0019c58f irr::createDevice(irr::video::E_DRIVER_TYPE, irr::core::dimension2d<int> const&, unsigned int, bool, bool, bool, irr::IEventReceiver*, char const*) + 95
15 MAVs3D 0x00007418 IrrlichtGUI::IrrlichtGUI() + 96
16 MAVs3D 0x0000773c Simulator::Simulator() + 34
17 MAVs3D 0x00007274 main + 34 (main.cpp:15)
18 MAVs3D 0x00006bdb _start + 209
19 MAVs3D 0x00006b09 start + 41
Thread 1:
0 libSystem.B.dylib 0x9697368e __semwait_signal + 10
1 libSystem.B.dylib 0x9699e36d pthread_cond_wait$UNIX2003 + 73
2 libGLProgrammability.dylib 0x9598bb32 glvmDoWork + 162
3 libSystem.B.dylib 0x9699d6f5 _pthread_start + 321
4 libSystem.B.dylib 0x9699d5b2 thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x01409ed0 ecx: 0x00000000 edx: 0x00000008
edi: 0x0000030a esi: 0x00000400 ebp: 0xbfffedf8 esp: 0xbfffedc0
ss: 0x0000001f efl: 0x00010246 eip: 0x00209baa cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000
Cheers,
Fabio
Error when creating a device on a MacBook Air
-
hybrid
- Admin
- Posts: 14143
- Joined: Wed Apr 19, 2006 9:20 pm
- Location: Oldenburg(Oldb), Germany
- Contact:
This error had been reported before, but now the stack trace at least supports my assumptions: It looks like the event handler creates a change on the not yet fully created driver or window or something. However, I couldn't find this problem on a first glance through the OSX device. Maybe varmint can help, try to PM him or get him on IRC.
No worries. Fortunately I've got my computer at work and so I can write (and run) my applications there. Anyway I'm happy (I know, it sounds a bit sad... but that's the way it is... :p) to know that I'm not the only person having ever experienced this problem on a Air.hybrid wrote:This error had been reported before, but now the stack trace at least supports my assumptions: It looks like the event handler creates a change on the not yet fully created driver or window or something. However, I couldn't find this problem on a first glance through the OSX device. Maybe varmint can help, try to PM him or get him on IRC.
