in reply to panic: COND_DESTROY(6)
You could provide a little more info perhaps?
- OS?
- Perl version?
- threads version?
- threads::shared version?
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:
#define COND_DESTROY(c) \ STMT_START { \ (c)->waiters = 0; \ if (CloseHandle((c)->sem) == 0) \ Perl_croak_nocontext("panic: COND_DESTROY (%ld)",GetLastError( +)); \ } STMT_END
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.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: panic: COND_DESTROY(6)
by menth0l (Monk) on Jan 26, 2012 at 15:09 UTC | |
by BrowserUk (Patriarch) on Jan 26, 2012 at 15:29 UTC | |
by menth0l (Monk) on Jan 27, 2012 at 08:07 UTC | |
Re^2: panic: COND_DESTROY(6)
by menth0l (Monk) on Jan 27, 2012 at 08:33 UTC | |
by BrowserUk (Patriarch) on Jan 27, 2012 at 09:09 UTC | |
by menth0l (Monk) on Jan 27, 2012 at 11:33 UTC | |
by BrowserUk (Patriarch) on Jan 27, 2012 at 11:45 UTC | |
by menth0l (Monk) on Jan 27, 2012 at 11:53 UTC | |
| |
by chrestomanci (Priest) on Jan 27, 2012 at 10:54 UTC |