12

I've looked around and never found a comprehensive list of exit codes for Xcode especially working with iOS. This question: Debuging to simulator crashes with "exited with status 5" unless I have breakpoint simply says I need to restart xcode to solve a common problem labeled 'exit code 5'. There are many other similar questions out there. The solutions often work, however I don't understand how they work. Next time I come across once of these exit code's I'd like to know what they mean so I can have a better idea of how to prevent it from happening again.

What are the common Xcode signals and exit codes?

4
  • A duplicate of this: stackoverflow.com/questions/2504512/… Commented May 23, 2011 at 19:00
  • I'm going to reword the question to simply ask for a list of signals if thats okay. Now there is no need to mention my particular problem... Also in my defense there still is no accepted answer for this 'Duplicated question' as I mentioned that didn't work so I wanted to solve my problem by getting what exit code 5 meant. Commented May 24, 2011 at 10:16
  • You should further detail the original question, not open a new one just to ask people for an answer. Just give people time to read, find and appropriately answer Commented May 24, 2011 at 11:51
  • Okay I've reworded the question I hope people find it much clearer, I don't think the question is really about Exit Code 5 nearly so much as what are the signals. With this change I'll also accept Grady's Answer Commented May 27, 2011 at 4:45

1 Answer 1

12

signal 0 an 1 are pretty standard, others are defined in context and by users, on osx 10.6:

man signal gives:

 2 SIGINT terminate process interrupt program 3 SIGQUIT create core image quit program 4 SIGILL create core image illegal instruction 5 SIGTRAP create core image trace trap 6 SIGABRT create core image abort program (formerly SIGIOT) 7 SIGEMT create core image emulate instruction executed 8 SIGFPE create core image floating-point exception 9 SIGKILL terminate process kill program 10 SIGBUS create core image bus error 11 SIGSEGV create core image segmentation violation 12 SIGSYS create core image non-existent system call invoked 13 SIGPIPE terminate process write on a pipe with no reader 14 SIGALRM terminate process real-time timer expired 15 SIGTERM terminate process software termination signal 16 SIGURG discard signal urgent condition present on socket 17 SIGSTOP stop process stop (cannot be caught or ignored) 18 SIGTSTP stop process stop signal generated from keyboard 19 SIGCONT discard signal continue after stop 20 SIGCHLD discard signal child status has changed 21 SIGTTIN stop process background read attempted from control terminal 22 SIGTTOU stop process background write attempted to control terminal 23 SIGIO discard signal I/O is possible on a descriptor (see fcntl(2)) 24 SIGXCPU terminate process cpu time limit exceeded (see setrlimit(2)) 25 SIGXFSZ terminate process file size limit exceeded (see setrlimit(2)) 26 SIGVTALRM terminate process virtual time alarm (see setitimer(2)) 27 SIGPROF terminate process profiling timer alarm (see setitimer(2)) 28 SIGWINCH discard signal Window size change 29 SIGINFO discard signal status request from keyboard 30 SIGUSR1 terminate process User defined signal 1 31 SIGUSR2 terminate process User defined signal 2 
Sign up to request clarification or add additional context in comments.

11 Comments

true, but if an application is killed with a signal, they can use that as the exit code, dont know if xcode does, but i have done it.
SIGTRAP doesn't kill a process.
Exception Type: EXC_CRASH (SIGTRAP) Exception Codes: 0x0000000000000000, 0x0000000000000000
that would also explain why the debugger being enabled would make it not crash.
Uh, what? That's not an exit code. That's an exception. The process doesn't even get a chance to emit an exit code in that case.
|

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.