This is the mail archive of the
mailing list for the GCC project.
Re: Throwing exception in constructor causes segfault
- From: Andreas Schwab <schwab at suse dot de>
- To: Craig Rodrigues <rodrigc at attbi dot com>
- Cc: libstdc++ at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Sat, 23 Feb 2002 21:56:48 +0100
- Subject: Re: Throwing exception in constructor causes segfault
- References: <20020223150023.A3639@attbi.com>
Craig Rodrigues <email@example.com> writes:
|> I don't know how this stuff works, but I am guessing
|> that for some reason, during the stack unwinding, the
|> destructor is being called on *p, even though it
|> is not fully constructed, and this is causing problems.
|> Does anyone have any ideas about this?
The problem is that operator delete() is receiving a different address
than returned by operator new(). It looks like it is not adjusted for
Andreas Schwab, SuSE Labs, firstname.lastname@example.org
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."