Segmentation fault Causes

Segmentation fault Causes

[Daniel Bolgheroni]

What are the causes that a program can give an error "Segmentation fault (core dumped)"?

I'm compiling a program I'm writing but I getting some of this error messages executing it. I looked into gcc FAQ and gcc 2.95 manual, but I found no references to this problem.

I'm using the following version of gcc:

gcc version 2.95.3 20010315 (release) (NetBSD nb3)

Thank you.

RE: Segmentation fault Causes

[J.C.Wren]

	Most commonly it's caused by trying to write to a pointer that either is
uninitialized, or NULL.

int main (int argc, char **argv)
{
   char *p = NULL;
   *p = 'A';
}

will cause a segfault.  Also, if 'p' isn't assigned an explicit value, it
will have whatevers on the stack at that point.  Another thing that will
cause a segfault is writing passed the end of an array:

int main (int argc, char **argv)
{
   char buffer [16];
   memset (buffer, 0, 64);
}

will segfault.

	I would suggest compiling your program with the -W and -Wall switches
('gcc -W -Wall myprog.c -o myprog').  Fix any and all warnings.  GCC is very
good about warning about usage of uninitialized variables.

	If you want to see how far you're getting in your program use 'fprintf
(stderr, "Got to line %d\n", __LINE__);'.  This will show how far you've got
before the segfault occurs.  You must write to stderr and not stdout because
of buffering.  When the program segfaults, unbuffered I/O will NOT be
written to the console.  This is why people often make the mistake of saying
'printf ("Got to line %d\n", __LINE__);' and thinking they really didn't get
that far.  In reality, it did get that far, but the I/O was lost when the
buffer remained unflushed after the segfault.  There are some exceptions to
this rule, but it's not worth pursuing at this point (just so someone does
say "but if you set unbuffered I/O mode, that doesn't apply!").

	--John


> -----Original Message-----
> From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org]On
> Behalf Of Daniel Bolgheroni
> Sent: Sunday, February 23, 2003 23:55
> To: gcc-help@gcc.gnu.org
> Subject: Segmentation fault Causes
>
>
> What are the causes that a program can give an error
> "Segmentation fault (core dumped)"?
>
> I'm compiling a program I'm writing but I getting some of
> this error messages executing it. I looked into gcc FAQ and
> gcc 2.95 manual, but I found no references to this problem.
>
> I'm using the following version of gcc:
>
> gcc version 2.95.3 20010315 (release) (NetBSD nb3)
>
> Thank you.

Segmentation fault Causes

[Daniel Bolgheroni]

What are the causes that a program can give an error "Segmentation fault (core dumped)"?

I'm compiling a program I'm writing but I getting some of this error messages executing it. I looked into gcc FAQ and gcc 2.95 manual, but I found no references to this problem.

I'm using the following version of gcc:

gcc version 2.95.3 20010315 (release) (NetBSD nb3)

Thank you.

Re: Segmentation fault Causes

[bjorn rohde jensen]

Hi there,

  Segmentation faults are signals delivered from the operating
system to a process to inform it, that the process has attempted
to access memory outside its address space. Common causes are
forgetting to initialise a pointer before use or using something,
which is not a pointer, as a pointer.
  You might want to compile with debug info and run the program
under a debug'er. It should provide you with the exact line,
where the segfault is generated. If you are fairly lucky, the
reason will be also be quite apparent.

Yours sincerely,

Bjorn

Re: Segmentation fault Causes

[Dikandé Alain Moïse]

.. Most of core dumping signals indicate bad pointer adresses to your outputs/inputs. Check that your program is not trying to access a memory location 
outside its address.  Bad use of pointers cause bus errors and segmentation violations are typically
out-of-bounds array references, and/or references through uninitialized or
mangled pointers.  Look very closely in your program for bizarre things like
that.  A frequent example of bad use of pointers adress in C is:

        int b;
        scanf("%d", b);

When compiled, you will have the "segmentation fault" signal. Instead, with the correct version:

        int c;
        scanf("%d", &c);

No "segmentation fault message(core file) is given(generated). 

In  C++, a typical example is:

        int* q=new int[150];
        cout<< q[100];

instead of the correct version:

        int* Q=new int[200];
        cout << Q[199]

Good Kuck..

En réponse à Daniel Bolgheroni <dab__@uol.com.br>:

> What are the causes that a program can give an error "Segmentation fault
> (core dumped)"?
> 
> I'm compiling a program I'm writing but I getting some of this error
> messages executing it. I looked into gcc FAQ and gcc 2.95 manual, but I
> found no references to this problem.
> 
> I'm using the following version of gcc:
> 
> gcc version 2.95.3 20010315 (release) (NetBSD nb3)
> 
> Thank you.
> 
> 
> 



                      DIKANDÉ ALAIN MOÏSE
Present: CERPEMA, Département de Physique, fac. Sciences, Univ. Sherbrooke J1k-2R1 
Québec, Canada. tel: (819)821-8000 ext. 3043.
Permanent: Département de Physique, Faculté des Sciences, Université de Douala BP 24157 Douala, Cameroun.

"Le mépris des autres et des choses, plutôt que nous grandir, nous rabaisse et 
met en péril notre capacité de compréhension du monde et de l' humanité". 
Albert Einstein.

RedHat 8.0 `istream_iterator' undeclared (first use this function)

[MR]

Hello STL gurus, 


I have a bit of a problem getting my iterators to work with libstdc++
3.2-7 (redhat 8.0), GCC 3.2.

with a very simple program (merges two files):

#include <iostream>
#include <fstream>
#include <algorithm>

using namespace std;

main(int argc, char**argv) {
    if (argc < 3) {

	cout << "You must supply two input files.\n";

	exit(1);
    }

    ifstream in1(argv[1]), in2(argv[2]);
    if(!in1||!in2) {
	cout << "File open error\n";
	exit(1);
    }

    merge(
	istream_iterator<float>(in1),
	istream_iterator<float>(),
	istream_iterator<float>(in2),
	istream_iterator<float>(),
	ostream_iterator<float>(cout, "\n")
    );
    return 0;
}

I get the following complaints from the compiler:
algdemo.cpp:22: `istream_iterator' undeclared (first use this function)
algdemo.cpp:22: (Each undeclared identifier is reported only once for
each 
   function it appears in.)
algdemo.cpp:22: parse error before `>' token


I call the compile with g++ -g -Wall algdemo.cpp


So where am I going wrong?  What do I need to do to get the
istream_iterators and ostream_iterators to work?

Thanks for your help, it is greatly appreciated.

Matt

Re: RedHat 8.0 `istream_iterator' undeclared (first use this function)

[Oscar Fuentes]

MR <nimrod.bm@optusnet.com.au> writes:

[snip]

> I get the following complaints from the compiler:
> algdemo.cpp:22: `istream_iterator' undeclared (first use this function)
[snip]

#include <iterator>

-- 
Oscar

Re: RedHat 8.0 `istream_iterator' undeclared (first use this function)

[LLeweLLyn Reese]

MR <nimrod.bm@optusnet.com.au> writes:

> Hello STL gurus, 
> 
> 
> I have a bit of a problem getting my iterators to work with libstdc++
> 3.2-7 (redhat 8.0), GCC 3.2.
> 
> with a very simple program (merges two files):
> 
> #include <iostream>
> #include <fstream>
> #include <algorithm>

#include <iterator>

Stream iterators are in this header. See the <iterator> synopsis in
    24.2, or 24.5 .

> 
> using namespace std;
> 
> main(int argc, char**argv) {

int main(int argc, char**argv) {

>     if (argc < 3) {
> 
> 	cout << "You must supply two input files.\n";
> 
> 	exit(1);
>     }
> 
>     ifstream in1(argv[1]), in2(argv[2]);
>     if(!in1||!in2) {
> 	cout << "File open error\n";
> 	exit(1);
>     }
> 
>     merge(
> 	istream_iterator<float>(in1),
> 	istream_iterator<float>(),
> 	istream_iterator<float>(in2),
> 	istream_iterator<float>(),
> 	ostream_iterator<float>(cout, "\n")
>     );
>     return 0;
> }