|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
What's the difference between Segmentation fault and Bus error and Illegal...?
Post 302179655 by lakeat on Friday 28th of March 2008 09:25:14 AM
03-28-2008
Quote:
Segmentation Fault (also known as SIGSEGV and is usually signal 11) - You can get this message when the program tries to write/read outside the memory allocated for it or when writing memory which can only be read
Bus Error (also known as SIGBUS and is usually signal 10) - You can encounter this signal error when an invalid pointer is dereferenced i.e when you try to dereference an uninitialised pointer. It is similar to SIGSEGV but the difference is that SIGSEGV indicates an invalid access to valid memory, while SIGBUS indicates an access to an invalid address.
Illegal Instructions (also known as SIGILL and is usually signal 4) - This usually means that your program is trying to execute garbage or a privileged instruction. You might encounter this -
(a.) when you try to execute data
(b.) when you try to execute a corrupted executed file.
(c.) stack overflows
(d.) when the system has trouble running the handler for a signal
HTH
Bus Error (also known as SIGBUS and is usually signal 10) - You can encounter this signal error when an invalid pointer is dereferenced i.e when you try to dereference an uninitialised pointer. It is similar to SIGSEGV but the difference is that SIGSEGV indicates an invalid access to valid memory, while SIGBUS indicates an access to an invalid address.
Illegal Instructions (also known as SIGILL and is usually signal 4) - This usually means that your program is trying to execute garbage or a privileged instruction. You might encounter this -
(a.) when you try to execute data
(b.) when you try to execute a corrupted executed file.
(c.) stack overflows
(d.) when the system has trouble running the handler for a signal
HTH
I wonder is there any good book on unix or linux debugging?
Could anybody recommend one?
Daniel
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
While comparing primary key data of two tables thr bteq script I am getting this Error. This script is a shell script.
*** Error: The following error was encountered on the output file.
Script.sh: 3043492 Segmentation fault(coredump)
Please let me know how to get through it.
... (5 Replies)
Discussion started by: monika
5 Replies
2. UNIX for Advanced & Expert Users
hi all
is there any way to capture the segmentation fault error when i run sqsh on a unix shell script.
Ex:
#!/bin/ksh
sqsh -S "server" -U "user" -P "pwd" << EOF
use mydb
go
exec proc1
go
exit
EOF
retval=$?
echo "sqsh return value $retval"
if
then
exit (1 Reply)
Discussion started by: sudheer1984
1 Replies
3. Shell Programming and Scripting
Hi all,
I have a folder with some 28 files. I have a script file that will iteratively take one file at a time from the folder and provide an output for the input file. Till the 7th file, there was no problem but from the 8th file onwards, i got this Segmentation Fault(Core Dump) error. A file... (2 Replies)
Discussion started by: mick_000
2 Replies
4. Programming
i am executing following program
int main()
{ char str;
FILE * fp;
int i=0; ... (4 Replies)
Discussion started by: bhavesh.sapra
4 Replies
5. Programming
i have this code
int already_there(char *client_names, char *username) {
int i;
for(i = 0; i<NUM; i++) {
printf("HERE\n");
if (strcmp(client_names, username)==0) return(1);
}
return(0);
}
and i get a segmentation fault, whats wrong here? (7 Replies)
Discussion started by: omega666
7 Replies
6. UNIX for Advanced & Expert Users
What does this mean and why is this happening?
$ ps -ef | grep ocular
Segmentation fault (core dumped)
$ ps -ef | grep ocular
Segmentation fault (core dumped)
$ ps aux | grep ocular
Segmentation fault (core dumped)
$ ps
Segmentation fault (core dumped)
$ pkill okular
$ ps... (1 Reply)
Discussion started by: cokedude
1 Replies
7. UNIX for Dummies Questions & Answers
#include<stdio.h>
#include<malloc.h>
#include<unistd.h>
#include<stdlib.h>
void *start_1(void *argv)
{
printf("thread 0x%x\n",(unsigned int)pthread_self());
pthread_exit((void*)1);
}
void *start_2(void *argv)
{
printf("thread 0x%x\n",(unsigned int)pthread_self());
return (void*)2;
}... (2 Replies)
Discussion started by: vincent__tse
2 Replies
8. Programming
I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this :
i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Discussion started by: pooyair
6 Replies
9. Programming
Hello guys, i have this code:
int main(int argc, char *argv) {
int i, j, N, result = 0, **vec;
if (argc < 2) {
fprintf(stderr, "Usage: %s N\n", argv);
}
/* ... how many numbers to read */
N = atoi(argv);
/* check if N is a power of two; exit if not */
if (!... (3 Replies)
Discussion started by: DinisR
3 Replies
10. Programming
Oddities with gcc, 2.95.3 for the AMIGA and 4.2.1 for MY current OSX 10.14.1...
I am creating a basic calculator for the AMIGA ADE *NIX emulator in C as it does not have one.
Below are two very condensed snippets of which I have added the results inside the each code section.
IMPORTANT!... (11 Replies)
Discussion started by: wisecracker
11 Replies
LEARN ABOUT LINUX
bosskill
BOSSKILL(8) System Manager's Manual BOSSKILL(8) NAME
bosskill - send a signal to your boss, or terminate your boss SYNOPSIS
bosskill [ -signal ] <bossname> DESCRIPTION
bosskill sends the TERM (terminate, 15) signal to the boss with the specified bossname. If a signal name or number preceded by `-' is given as the first argument, that signal is sent instead of terminate. The killed boss must be in the system administrator's supervisory chain. The following is a list of all signals with names as in the include file <signal.h>: SIGHUP 1 hangup. Forces bossname to re-read his/her job description and figure out that he/she knows squat about sysadmin work or life, in general. SIGINT 2 interrupt. Prevents the bossname from interrupting the sysadmin for one hour. SIGQUIT 3 quit. Causes the boss to quit his/her job with no explanation. SIGILL 4 illegal instruction. Makes the boss believe the last instruction he/she gave was illegal, so he/she withdraws it. SIGTRAP 5 trace trap. Display the exact location of the boss. SIGABRT 6 abort. Makes the boss go home and try again tomorrow. SIGKILL 9 kill. Game over. SIGBUS 10 bus error. Boss's transportation fails on the way to work. SIGSEGV 11 segmentation violation. Boss realizes he/she is trying to do something for which he/she is not quailified and stops. SIGSYS 12 bad argument. Boss loses. SIGPIPE 13 smoke pipe. Boss samples some green leafy substance and mellows out. SIGALRM 14 alarm. Boss is startled and falls over. Best used when boss is walking next to his/her boss. SIGTERM 15 termination signal. Boss is fired. BUGS
Sending a SIGABRT to a boss that is already home will cause him/her to walk aimlessly in circles for two hours. HISTORY
Written by Eric L. Pederson <eric@bofh.org.uk>. 27 September 1995 BOSSKILL(8)