#14928: [kernel] PANIC: Destroying condition variable entry but it's still
attached
to variable
-----------------------------+----------------------------
Reporter: diver | Owner: mmlr
Type: bug | Status: assigned
Priority: normal | Milestone: R1/beta2
Component: System/Kernel | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
-----------------------------+----------------------------
Comment (by waddlesplash):
{{{
<mmlr> the condvar thing is a bit of a nuisance
<mmlr> it really is only a debug thing
<mmlr> nothing bad actually happens
<mmlr> but it's a warning for a possible problem that is nice to keep
<waddlesplash> there isn't a 2 line fix?
<mmlr> it just means that the entry needs to be removed in all error cases
<mmlr> so an autodeleter may work for that
<mmlr> but from a performance overhead that's a bit stupid
<mmlr> so moving the addition of the entry further down is the most
sensible thing to do
<mmlr> but it's important where it ends up as it must be ensured that it
is added before the team becomes externally visible (and may therefore
cause the code path to trigger that needs the entry to be there)
<mmlr> and unfortunately it isn't exactly obvious where that is
<waddlesplash> ok. well, whenever you have 10-20 minutes to do this,
that's fine
<mmlr> well, the quick fix would be an autodeleter
<mmlr> but the right one is to move it
<mmlr> I've spent some time trying to find the right spot but as I said
it's not exactly obvious
<mmlr> and moving it too far would obviously be bad
}}}
--
Ticket URL: <https://dev.haiku-os.org/ticket/14928#comment:4>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
