|more useful options|
Re: panic: COND_DESTROY(6)by BrowserUk (Pope)
|on Jan 26, 2012 at 14:35 UTC||Need Help??|
You could provide a little more info perhaps?
Am i thinking right that the "6" is a TID of thread that crashed?
More likely the number is the numeric error code. On Windows that would be "invalid handle" returned from the attempt to close the semaphore associated with a threads::shared condition variable:
Of course it might mean something different on other OSes.
Your best bet would be to post the code, assuming it isn't too large or proprietary or require too much in the way of unique set-up.
If it is, then try to reduce as much as possible whilst still having the error occur. (I appreciate that can be difficult with transient errors like this.) But it will be very hard to advise without sight of the code in question.
If it is the invalid handle problem, the most likely cause is the handle being closed twice, but working out how that might occur will require sight of the code.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.