This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
AW: g++ 2.95.3: throw does zero byte malloc?
- To: "Bernd Schmidt" <bernds at cambridge dot redhat dot com>,"Sebastian Rittau" <srittau at jroger dot in-berlin dot de>
- Subject: AW: g++ 2.95.3: throw does zero byte malloc?
- From: "Hugo Mildenberger" <Hugo dot Mildenberger at topmail dot de>
- Date: Wed, 21 Feb 2001 07:56:12 +0100
- Cc: <gcc-bugs at gcc dot gnu dot org>
Yes, same with 2.95.2.
Hugo Mildenberger
-----Ursprungliche Nachricht-----
Von: gcc-bugs-owner@gcc.gnu.org [mailto:gcc-bugs-owner@gcc.gnu.org]Im
Auftrag von Bernd Schmidt
Gesendet: Mo, 19. Februar 2001 14:25
An: Sebastian Rittau
Cc: gcc-bugs@gcc.gnu.org
Betreff: Re: g++ 2.95.3: throw does zero byte malloc?
On Sat, 17 Feb 2001, Sebastian Rittau wrote:
> Consider the following program:
>
> | int main(int argc, char **argv)
> | {
> | throw 5;
> | }
>
> If I compile and link this with libefence (electric-fence malloc
> debugger), efence claims that a zero byte memory allocation is made:
Does it happen with 2.95.2 as well?
Bernd