--- Comment #10 from Andreas dot Kowarz at tu-dresden dot de 2007-03-12
09:30 ---
THS (The Holy Standard :-) ) 3.7.4.2/3 reads to me that for standard library
implementations the delete operators must be called in any case but return
immediately if the first argument is NULL = NULL
--- Comment #8 from Andreas dot Kowarz at tu-dresden dot de 2007-03-09
09:37 ---
It seems that the bug triggers only when returning NULL in the new operators.
Returning something different ( tested with (void *)1 ) is a workaround for the
problem. Checking for not returning NULL
gnu dot org
ReportedBy: Andreas dot Kowarz at tu-dresden dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29163
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: Andreas dot Kowarz at tu-dresden dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29164
--- Comment #1 from Andreas dot Kowarz at tu-dresden dot de 2006-09-21
10:47 ---
*** This bug has been marked as a duplicate of 29164 ***
--
Andreas dot Kowarz at tu-dresden dot de changed:
What|Removed |Added
--- Comment #1 from Andreas dot Kowarz at tu-dresden dot de 2006-09-21
10:47 ---
*** Bug 29163 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29164
--- Comment #3 from Andreas dot Kowarz at tu-dresden dot de 2006-09-21
11:59 ---
(In reply to comment #2)
EDG ends up not even calling the overloaded delete. Looking at the std I can
see no reason why your program should not use the overloaded deletes.
For the moment, I can work
