public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: flatmax@ieee.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/6216: seg fault when using new to create a memory array
Date: Sun, 15 Sep 2002 11:25:00 -0000	[thread overview]
Message-ID: <20020915182549.5385.qmail@sources.redhat.com> (raw)

Synopsis: seg fault when using new to create a memory array

State-Changed-From-To: open->feedback
State-Changed-By: nathan
State-Changed-When: Sun Sep 15 11:25:48 2002
State-Changed-Why:
    I can't copmpile this with the current CVS, because the
    header's no longer match the library. However, the
    symptoms you describe sound stunningly like you have an
    allocation problem. You are either writing off the end
    of a malloc'd array, or using a pointer after it's been
    freed. Try with a debugging malloc library,

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6216


             reply	other threads:[~2002-09-15 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-15 11:25 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06 22:29 bangerth
2002-04-07 10:26 flatmax

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=20020915182549.5385.qmail@sources.redhat.com \
    --to=nathan@gcc.gnu.org \
    --cc=flatmax@ieee.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).