Re: App does not start on a different machine
Re: App does not start on a different machine
- Subject: Re: App does not start on a different machine
- From: Rob Ross <email@hidden>
- Date: Wed, 10 Jun 2009 16:16:56 -0700
You could try adding logging statements after major milestones in your
start-up sequence, and see what the last one it writes is. That might
give you a clue how far it's getting (if at all) before it quits. It
you don't even see the first message (which you should add as the very
first line of main() ) then the problem may not be with the code
itself but with how XCode has built it.
Rob
On Jun 10, 2009, at 4:10 PM, Martin Batholdy wrote:
well, I am pretty unexperienced and new to writing programs on the
mac.
the app just creates two text files on start in a subfolder of the
"application support" folder in the library folder of the user.
Then it reads and writes stuff in there.
There are no external / exotic libraries.
It is really a pretty simple program and it is compiled in 32bit
universal (as seen in the project infos).
I haven't changed anything in the compile settings, have the latest
XCode version and the console does not say anything.
And it is a release version I tried on the other macBook.
ZeroLinker is off, when I change the build configuration to
"Release", right?
So I am pretty helpless with that issue, having no real experience
with building programs on the mac.
And as I said, the program works fine on my machine ...
Am 11.06.2009 um 00:43 schrieb vinai:
--- On Wed, 6/10/09, Martin Batholdy <email@hidden> wrote:
my app works fine on my macbook,
but on a macbook pro it starts and then just disappears
immediately after the start
(nor error message).
The OS version is the same,
and the app is pretty simple (no graphic stuff or something
like that).
There are no errors or warnings in the code ... and as I
said, the app works fine on my machine.
why could that be?
You didn't provide a whole lot of information for us to go on, but
just from the info you provided, the only things I could think of
are external library dependencies, or user permission to run the
application, or are you malloc'ing a huge amount of RAM on one
machine that you don't have on the other machine ?
As another tip, I've had good luck debugging stuff by opening up OS
X's terminal, and from the command line of the terminal, running
the binary of the application itself from terminal's command line;
something akin to:
$ cd YourApp.app/Contents/MacOS/
$ ./YourApp
This will output debugging info from fprintf's or NSLog's in your
code to the terminal command line. IIRC, this is equivalent to
running the program from XCode's "Build and Run" option, where you
get a logging terminal. So if nothing shows up there, I am not
sure how useful this tip is.
But more info would be helpful ...
vinai
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden