bug: unlocking an invalid mutex
Andreas Ericsson
ae at op5.se
Fri Oct 26 17:34:22 CEST 2007
Geert Hendrickx wrote:
> On Sun, Oct 14, 2007 at 10:33:47AM +0200, Andreas Ericsson wrote:
>> I suppose just checking for success from the pthread_mutex_lock() calls
>> would be enough, and letting it spinlock for 10 tries if it fails. If it
>> *always* fails, that would be quite horrible though, as it would mean
>> something fairly illegal is going on in there.
>>
>> I'll whip up a patch for it once I'm done with what I'm currently fiddling
>> with.
>
>
> Have you been able to code a solution for this yet?
>
Nopes. Ahead of it in the todo are (besides my day-job and my girlfriend):
- Rewriting git-pull in C.
- Hacking some more on nagios config-reading replacement.
- Adding sub-topic help to git.
- Finishing the NEB for loadbalanced and distributed Nagios.
In roughly that order.
--
Andreas Ericsson andreas.ericsson at op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
More information about the Developers
mailing list