From: Eric Woodruff (Eric.Woodruff_at_[hidden])
Date: 2002-08-16 09:52:59
Would a runtime analyzer like Rational Purify, etc, detect a leak if there
was an implementation that didn't take the assumed path? If so, the example
can be proven unequivocally to either work or not work. Yes from a language
standpoint, it is mal-formed code, but not from a practical perspective.
----- Original Message -----
From: Carl Daniel
Sent: Friday, 2002:August:16 9:53 AM
Subject: Re: Threads & Exceptions - Safety Verification
"Eric Woodruff" <Eric.Woodruff_at_[hidden]> wrote in message
> Can anyone vouch for the safety of using boost::thread_exit () [which has
> yet to be implemented AFAIK] to allow exceptions to be propagated across
> threads on multiple platforms (besides the apparent working status of the
> pthread example below)?
Two BIG problems:
1. You're calling delete on an object which was not obtained by a
corresponding call to new - undefined loud boom happens.
2. Terminating a thread in the middle of a catch block is likely to cause
resources allocated by the exception propagation mechanism to be leaked -
unless, of course, boost:thread_exit is implemented by the compiler itself
and takes whatever steps are necessary.
Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk