Crash report on first run on OSX

Targets macOS
1

Hi all,

I’ve written an app for the windows platform and now I want to compile/run it also on OSX (first try ever).

The program compiles without errors, but does not start (debugged or build). I get the following report:
My knowledge of OSX is very limited, so I would really appreciate if someone could point me in the right direction of the error.

Thanks in advance!

Crash report:

Process:         AppPlayer.debug [317]
Path:            /Users/USER/Desktop/*/AppPlayer.debug.app/Contents/MacOS/AppPlayer.debug
Identifier:      com.onetwo
Version:         ??? (1.0.0.0.50)
Code Type:       X86 (Native)
Parent Process:  launchd [138]
User ID:         501

Date/Time:       2014-11-19 09:19:23.964 +0100
OS Version:      Mac OS X 10.8.3 (12D78)
Report Version:  10

Interval Since Last Report:          182419 sec
Crashes Since Last Report:           68
Per-App Crashes Since Last Report:   4
Anonymous UUID:                      7B0B5C96-0D55-F84F-457D-C789A635AE76

Crashed Thread:  0

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: /System/Library/Frameworks/user32.framework/user32
  Referenced from: /Users/USER/Desktop/*/AppPlayer.debug.app/Contents/MacOS/AppPlayer.debug
  Reason: image not found

Binary Images:
    0x1000 -   0x738c83 +com.onetwo (??? - 1.0.0.0.50) <494DF0E7-239F-33BE-B0F2-6A8F1C468697> /Users/USER/Desktop/*/AppPlayer.debug.app/Contents/MacOS/AppPlayer.debug
  0x7bb000 -   0x92bff3 +rbframework.dylib (1) <ED875D5A-25B3-36D0-AF94-9A814477C2A3> /Users/USER/Desktop/*/AppPlayer.debug.app/Contents/Frameworks/rbframework.dylib
0x8fed2000 - 0x8ff04e57  dyld (210.2.3) <23516BE4-29BE-350C-91C9-F36E7999F0F1> /usr/lib/dyld

Model: VMware7,1, BootROM VMW71.00V.0.B64.1310020058, 2 processors, 3.33 GHz, 8 GB, SMC 1.25f4
Graphics: VMware SVGA II, VMware SVGA II, PCI, 128 MB
Memory Module: RAM slot #0/RAM slot #0, 8 GB, DRAM, 0 MHz, VMware Virtual RAM, VMW-8192MB
Network Service: Ethernet, Ethernet, en0
Parallel ATA Device: VMware Virtual IDE CDROM Drive
SCSI Device: SCSI Target Device @ 0
USB Device: VMware Virtual USB Hub, 0x0e0f  (VMWare, Inc.), 0x0002, 0x11200000 / 3
USB Device: VMware Virtual USB Keyboard, apple_vendor_id, 0x020b, 0x11210000 / 4
USB Device: VMware Virtual USB Mouse, 0x0e0f  (VMWare, Inc.), 0x0003, 0x11100000 / 2
3

Thanks @jean-paul devulder ! There was indeed one declare I forgot to surround with #if. Pity the analyser can’t catch such errors (to my knowledge)

4

It mostly can’t tell.
You could actually write a dylib called user32 and place it on your system in an appropriate path and then declare into it on OS X.
The same is true going from OS X to Windows or Linux.
Then it would be valid to declare into user32.

And, dylibs/dll’s/.so’s being dynamically linked they don’t have to be present when you compile.

5

It’s not a huge problem @Norman Palardy . I was just thinking the IDE could maybe recognize Windows type declares automatically and give a warning when you analyse. But I have no idea if OSX declares and Windows declares can be distinguished.

As said, it’s my very first Xojo project for OSX and I have to get used to its error reporting. Somewhat different than on windows.

6

While declares into OS X frameworks done in Obj-C do use a different syntax a declare into a system library like libz will use much the same style as one from Windows. So they’re not really recognizable just based on the declare.

OS X crash logs tend to be really useful with full stack traces.
Even this one says whats wrong
Dyld Error Message:
Library not loaded: /System/Library/Frameworks/user32.framework/user32

Which literally means “I can’t find a dylib called user32” and the only time you get one of these at app start up is when its NOT a soft declare. The app tries to load the referenced dylib at launch when they are not soft declares.

7

Thanks for the clarification @Norman Palardy !