Help: Unwinding the C++ stack...throw, longjmp & threads

[Mike Stump]

> Date: Tue, 24 Aug 1999 19:52:19 -0500 (CDT)
> From: Josh Stern <jstern@citilink.com>

> Of course the chance of getting a signal that you want to throw on
> just as malloc() returns, combined with the situation where you
> actually care about the memory leak at this juncture, combined with
> the situation where the last catch that is released isn't going to
> just free a whole epoch of allocations, is an extremely low
> probability circumstance.

My guess is that you haven't thought about this long enough to use it.
Anyway, doesn't matter what I think...  Use the tool to the best of
your ability and ask us when it doesn't make sense, and we can clarify
any remaining details for you...

I just worry that you might expect more to work than will actually
work.

> I understood the example but thought of this case as being lost in
> the 'noise'.

See above.