I tried to target 10.6 and deploy to 10.6, build and run. Again it hangs up and the console says only:
[Switching to process 16132 thread 0x0] sharedlibrary apply-load-rules all (gdb)
In other words the "unable to read unknown load command" lines are gone, but it still hangs up before my code. I selected Pause and three threads are showing. None are my code; they all appear to be in MacOS prior to launch. Below are what is listed for the three threads (the starred line is the one with the green arrow in the debugger). Notice the code fragment for Thread 1 and 3 are identical. Also, thread 3 says WebCore: IconDatabase, which seems to tie in that many users can get it running by deleting the ~/Library/Icons folder before starting. I haven't deleted that folder in my computer yet because I think it should fixed without needing that step. Also two users claim deleting the folder does not halve them, Does anyone know what these threads mean?
Thread 1 com.apple.mainpthread
0x9911286c <+0000> mov $0x12d,êx 0x99112871 <+0005> call 0x9911449a <_sysenter_trap> *0x99112876 <+0010> jae 0x99112886 <__psynch_mutexwait+26> 0x99112878 <+0012> call 0x9911287d <__psynch_mutexwait+17> 0x9911287d <+0017> pop íx 0x9911287e <+0018> mov 0x1393f79f(íx),íx 0x99112884 <+0024> jmp *íx 0x99112886 <+0026> ret 0x99112887 <+0027> nop
Thread 2 com.apple.libdispatch-manager
0x99113900 <+0000> mov $0x16b,êx 0x99113905 <+0005> call 0x9911449a <_sysenter_trap> *0x9911390a <+0010> jae 0x9911391a <kevent+26> 0x9911390c <+0012> call 0x99113911 <kevent+17> 0x99113911 <+0017> pop íx 0x99113912 <+0018> mov 0x1393e70b(íx),íx 0x99113918 <+0024> jmp *íx 0x9911391a <+0026> ret 0x9911391b <+0027> nop
Thread 3 WebCore: IconDatabase
0x9911286c <+0000> mov $0x12d,êx 0x99112871 <+0005> call 0x9911449a <_sysenter_trap> *0x99112876 <+0010> jae 0x99112886 <__psynch_mutexwait+26> 0x99112878 <+0012> call 0x9911287d <__psynch_mutexwait+17> 0x9911287d <+0017> pop íx 0x9911287e <+0018> mov 0x1393f79f(íx),íx 0x99112884 <+0024> jmp *íx 0x99112886 <+0026> ret 0x99112887 <+0027> nop I noticed this set of events on the Cocoa threads.
Have you tried to build in Xcode 4.0.2? Also does it do that when you target 10.6 and deploy for 10.6?
The warnings you say, I usually try to build with relatively low number of warnings. Could it be they are causing any of these issues? Could you post these warnings?
The "M" just means the MainMenu.nib was modified against the local git repository you created. Unless you did a drastic change to the MainMenu.nib it should be fine.
- Cody
On Jul 26, 2011, at 10:57 AM, John Nairn wrote:
I installed Lion and XCode 4.1. I am trying to fix my app, which will not Launch in Lion (although some users say that can get it running fine by deleting the ~/Library/Icons folder first). My app used to target 10.5 and deploy 10.4. I could not target 10.5 on Lion (seems no SDK and I didn't try to find out how to get it yet and want to target newer anyway). I can build by targeting 10.6 and deploying 10.4 (although lots of warning that will need future attention, but unrelated to current problem). After building and running, it will not enter my code. It hangs up before it gets to -applicationWillFinishLaunching. The console repeats these messages
unable to read unknown load command 0x24
unable to read unknown load command 0x26
unable to read unknown load command 0x24
unable to read unknown load command 0x26
etc.
I also noticed an "M" icon next to my MainMenu.nib file and it was the only nib file that had such an Icon. That is the nib that should load at launch time. It instantiates an AppController object which has the -applicationWillFinishLaunching that does not get called and has its own +initialize that never is called either.
---------------
John Nairn
GEDitCOM - Genealogy Software for the Macintosh
http://www.geditcom.com
|