Re: exited with status (1) error
Re: exited with status (1) error
- Subject: Re: exited with status (1) error
- From: Scott Mitchell <email@hidden>
- Date: Thu, 13 Jul 2006 11:07:03 -0600
I don't know what I did but, I can run the Debugger now on the app.
So I think I am good for now. At least I can find out now why it is
not running correctly.
Thanks,
Scott Mitchell
On Jul 13, 2006, at 10:44 AM, Scott Mitchell wrote:
Well I was not using the release build of Xcode 2.3, on the Intel
Mac. I was using an older build. So I upgraded it to the correct
version, but I still get the same thing. So I try running it from
GDB and her is what I get. What does this mean exactly. Does anyone
know?
Program exited with code 055.
You can't do that when your target is 'None'.
You can't do that when your target is 'None'.
That is the Debug build.
If I try the release build here is what I get:
This GDB was configured as "i386-apple-darwin"...run: No such file
or directory.
"/Volumes/Development/Virtual Dashboard/build/Release/Virtual
Dashboard.app is not a core dump: File format not recognized.
When I do lipo -detailed_inof command on it shows that has both
architectures PPC and i386
I am totally at a loss.
I also tried an older version about a month old, and it launches
fine. I don't understand what is going on.
Thanks for any help,
Scott Mitchell
On Jul 13, 2006, at 6:03 AM, Paul Walmsley wrote:
Yep. That is where I am getting this error code, because for the
deployment build it looks like it launches and then just goes
away. I also tried just building it as a PPC app and the same
thing happens. Also tried removing some Frameworks that I had
added and commenting out the code for those frameworks, but still
get the error. It won't launch at all.
I've had similar problems before, so here's a few things to try:
* Are you using Xcode 2.3? If not, then upgrade then this fixes a
number of issues
* Switch to use the DWARF debugging format (which requires 2.3)
* Try running gdb from the console (I had problems where it would
work fine from the console but not from xcode itself). You also
may get a bit more information about where it's going wrong.
* Try disabling zerolink if it's on.
Paul
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40excelsiorsoftware.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40excelsiorsoftware.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden