public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8411: Segmentation fault error in malloc
Date: Thu, 31 Oct 2002 14:36:00 -0000	[thread overview]
Message-ID: <20021031223601.11826.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/8411; it has been noted by GNATS.

From: Joe Buck <jbuck@synopsys.com>
To: gcc-gnats@gcc.gnu.org, bridean@ureach.com, gcc-bugs@gcc.gnu.org
Cc:  
Subject: Re: c/8411: Segmentation fault error in malloc
Date: Thu, 31 Oct 2002 14:33:42 -0800

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8411
 
 Have you checked this program with a memory-checking tool (electric fence,
 valgrind, purify, etc) and verified that it doesn't have any memory 
 allocation
 errors (e.g. double-frees, writing beyond the end of an allocated 
 object, etc.).
 The most common cause of segmentation faults in malloc is this kind of 
 user error,
 and the problems tend to show up differently depending on optimization.
 


             reply	other threads:[~2002-10-31 22:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 14:36 Joe Buck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-23 21:06 neroden
2002-10-31 14:34 jbuck
2002-10-31  2:16 bridean

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=20021031223601.11826.qmail@sources.redhat.com \
    --to=jbuck@synopsys.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).