--- Comment #8 from dan dot colascione at gmail dot com 2010-02-16 23:43
---
Created an attachment (id=19895)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19895&action=view)
bad code
The code generated seems to violate the ABI exception handling specification
her
--- Comment #7 from dan dot colascione at gmail dot com 2010-02-16 23:07
---
Created an attachment (id=19894)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19894&action=view)
Minimal testcase
The leak triggered by the return in the 'catch' statement in c
--- Comment #5 from dan dot colascione at gmail dot com 2010-02-16 22:47
---
But the bug does not appear when compiling with gcc 4.4, which uses the same
unwinder.
--
dan dot colascione at gmail dot com changed:
What|Removed |Added
--- Comment #3 from dan dot colascione at gmail dot com 2010-02-16 22:43
---
Created an attachment (id=19893)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19893&action=view)
valgrind output showing the leak
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43099
--- Comment #2 from dan dot colascione at gmail dot com 2010-02-16 22:41
---
Also, compilation was done with just g++-mp-4.5 -m32 foo.cpp. The leak occurs
at all optimization levels.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43099
--- Comment #1 from dan dot colascione at gmail dot com 2010-02-16 22:40
---
Created an attachment (id=19892)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19892&action=view)
testcase
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43099
)
--
Summary: rethrowing leaks memory like a sieve
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dan dot colascione at gmail
