public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Bolgheroni <dab__@uol.com.br>
To: gcc-help@gcc.gnu.org
Subject: Segmentation fault Causes
Date: Tue, 22 Apr 2003 01:02:00 -0000	[thread overview]
Message-ID: <20030224045442.GA25932@uol.com.br> (raw)
Message-ID: <20030422010200.2pz3itiWKSiWMxSMPxpFDcSxhdr3K4sXmfna8vSWdNY@z> (raw)

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.


             reply	other threads:[~2003-04-22  1:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24  5:07 Daniel Bolgheroni [this message]
2003-02-24  5:22 ` J.C.Wren
2003-04-22  1:02 ` Daniel Bolgheroni
2003-04-22  7:47 ` bjorn rohde jensen
2003-04-22 18:24 ` Dikandé Alain Moïse
2003-05-24 11:07 ` RedHat 8.0 `istream_iterator' undeclared (first use this function) MR
2003-05-24 12:21   ` Oscar Fuentes
2003-05-24 12:50   ` LLeweLLyn Reese
2003-02-24  5:39 Segmentation fault Causes Ajay Bansal
2003-02-24  8:00 ` Sergei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030224045442.GA25932@uol.com.br \
    --to=dab__@uol.com.br \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).