This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/770
- To: nobody at gcc dot gnu dot org
- Subject: Re: c++/770
- From: neil at gcc dot gnu dot org
- Date: 11 Nov 2000 11:56:00 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: neil at gcc dot gnu dot org
The following reply was made to PR c++/770; it has been noted by GNATS.
From: neil@gcc.gnu.org
To: Tathagato.Rai.Dastidar@nsc.com, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/770
Date: 11 Nov 2000 11:54:52 -0000
Synopsis: Memory allocated by new remains accessible even after calling delete.
State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Sat Nov 11 03:54:52 2000
State-Changed-Why:
Not a bug.
>> Trying to access deallocated memory should give a core dump.
No, it gives undefined behaviour, which might include a core dump.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=770&database=gcc