@@ -130,15 +130,15 @@ triggered automatically by the runtime.
130
130
On macOS, we catch crashes and other events using a signal handler. At
131
131
time of writing, this is installed for the following signals:
132
132
133
- | Signal | | Description | Comment |
134
- | --------| ---------| ---------------------------| ------------------------------------------------------|
135
- | 3 | SIGQUIT | Quit program | |
136
- | 4 | SIGILL | Illegal instruction | |
137
- | 5 | SIGTRAP | Trace trap | |
138
- | 6 | SIGABRT | Abort program | |
139
- | 8 | SIGFPE | Floating point exception | On Intel, integer divide by zero also triggers this. |
140
- | 10 | SIGBUS | Bus error | |
141
- | 11 | SIGSEGV | Segmentation violation | |
133
+ | Signal | | Description | Comment |
134
+ | --------- | ---------| ---------------------------| ------------------------------------------------------|
135
+ | 3 | SIGQUIT | Quit program | |
136
+ | 4 | SIGILL | Illegal instruction | |
137
+ | 5 | SIGTRAP | Trace trap | |
138
+ | 6 | SIGABRT | Abort program | |
139
+ | 8 | SIGFPE | Floating point exception | On Intel, integer divide by zero also triggers this. |
140
+ | 10 | SIGBUS | Bus error | |
141
+ | 11 | SIGSEGV | Segmentation violation | |
142
142
143
143
If crash catching is enabled, the signal handler will be installed for
144
144
any process that links the Swift runtime. If you replace the handlers
0 commit comments