Throwing exception in constructor causes segfault

[Andreas Schwab]

Craig Rodrigues <rodrigc@attbi.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
the cookie.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
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."