Computer programs may throw SIGSEGV for improper memory handling (see segmentation fault). The operating system may inform the application of the nature of the error using the signal stack, which developers can use to debug their programs or handle errors.
The default action for a program upon receiving SIGSEGV is abnormal termination. This action will end the process, but may generate a core file to aid debugging, or perform some other platform-dependent action. For example, Linux systems using the grsecurity patch may log SIGSEGV signals in order to monitor for possible intrusion attempts using buffer overflows.
SIGSEGV can be caught; that is, applications can request what action they want to occur in place of the default. Examples of such action might be ignoring it, calling a function, or restoring the default action. In some circumstances, ignoring SIGSEGV results in undefined behavior.[1].
An example of an application that might handle SIGSEGV is a debugger, which might check the signal stack and inform the developer of what happened, and where the program terminated.
Originally Posted by angel_il
Надо запускать с опцией -force-overwrite, как я понимаю. Какая-то библиотека не перезаписывается. Какая именно мне установить не удалось, ибо SIGBUS "приходил" на разных приложениях к разным библиотекам. Но! Что важно - все библиотеки были из uclibc-opt. Вот такая вот кадриль.
