SIGSEGV, SIGBUS
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 407
- Joined: Mon Jun 27, 2005 8:54 am
- Location: Walker, Michigan
- Contact:
Re: SIGSEGV, SIGBUS
Usually bad code that caused a segmentation fault. It could also be failing hardware. Did anything get logged by the error daemon?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The UNIX command man signal will inform you about signals. Here are the most common ones. An asterisk indicates that a core image is dumped.
Code: Select all
Value Description
1 (SIGHUP) hangup
2 (SIGINT) interrupt
3* (SIGQUIT) quit
4* (SIGILL) illegal instruction
5* (SIGTRAP) trace trap
6* (SIGIOT) IOT instruction
7* (SIGEMT) EMT instruction
8* (SIGFPE) floating-point exception
9 (SIGKILL) kill (cannot be caught or ignored)
10* (SIGBUS) bus error
11* (SIGSEGV) segmentation violation
12* (SIGSYS) bad argument to system call
13 (SIGPIPE) write on a pipe with no one to read it
14 (SIGALRM) alarm clock
15 (SIGTERM) software termination signal
16 (SIGURG) urgent condition present on socket
17 (SIGSTOP) stop (cannot be caught or ignored)
18 (SIGTSTP) stop signal generated from keyboard
19 (SIGCONT) continue after stop
20 (SIGCHLD) child status has changed
21 (SIGTTIN) background read attempted from control terminal
22 (SIGTTOU) background write attempted to control terminal
23 (SIGIO) I/O is possible on a descriptor
24 (SIGXCPU) CPU time limit exceeded
25 (SIGXFSZ) file size limit exceeded
26 (SIGVTALRM) virtual time alarm
27 (SIGPROF) profiling timer alarm
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 24
- Joined: Mon Mar 14, 2005 6:42 pm
- Location: Minneapolis, Minnesota
Sorry, good ol' USA support engineers.
Yes we did receive a patch, and it resolved the SIGBUS/SIGSEGV errors that were coming from this bug. We now have been able to reenable time-based monitoring. Check with your support engineer for the patch under ecase e74035. We received a patch for both AIX and Sun.
Yes we did receive a patch, and it resolved the SIGBUS/SIGSEGV errors that were coming from this bug. We now have been able to reenable time-based monitoring. Check with your support engineer for the patch under ecase e74035. We received a patch for both AIX and Sun.