[Bug libstdc++/39237] New: Overloaded Operator delete not called
../lib64 -L/isv/gnu/bin/../lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../.. -L/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../../../lib64 -L/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../.. -L/lib/../lib64 -L/usr/lib/../lib64 simple_vector.o -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc /isv/gnu/bin/../lib/gcc-lib/x86_64-redhat-linux/3.2.3/crtend.o /isv/gnu/bin/../lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../../../lib64/crtn.o -- Summary: Overloaded Operator delete not called Product: gcc Version: 3.2.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: caroline dot rioux at ca dot ibm dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39237
[Bug libstdc++/39237] Overloaded Operator delete not called
--- Comment #1 from caroline dot rioux at ca dot ibm dot com 2009-02-18 21:39 --- Created an attachment (id=17327) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17327&action=view) Preprocessed source -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39237
[Bug libstdc++/39237] Overloaded Operator delete not called
--- Comment #3 from caroline dot rioux at ca dot ibm dot com 2009-02-18 22:02 --- (In reply to comment #2) > Fixed in 4.1.0 as mentioned already. 3.3.x is no longer maintained and any > bug > that is reported against that old version is most likely not going to be ever > fixed. > Ok thanks for your input. Was this explicitly fixed or a result of other framework changes? Is there any way a patch exists and could be applied? I ask because it is unlikely we will move to gcc4 in the short term. Is gcc3.4.x still supported? Because it also occurs there. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39237
[Bug libstdc++/39237] Overloaded Operator delete not called
--- Comment #5 from caroline dot rioux at ca dot ibm dot com 2009-02-18 22:15 --- (In reply to comment #4) > Nope, only currently 4.2 and above are being maintained. Is there a reason > why > you unlikely to move to 4.x in the short term? We have a big code base and changing compilers is done seldom and very carefully. This bug will be one more reason to move though, so that's good :) Is there any way you would know exactly what the bug is in this case? Is it a leak, or that the memory is not free'd through delete, or that the overloaded operator is not called when it should? I searched the bug database but couldn't find anything similar. Thanks again! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39237