bug: unlocking an invalid mutex

Geert Hendrickx ghen at telenet.be
Sun Oct 21 23:25:35 CEST 2007


On Thu, Oct 18, 2007 at 12:14:10PM -0500, Ethan Galstad wrote:
> Did you by chance have external commands disabled when you got the SIGABRT?
> 
> I believe the problem was due to the external_command_buffer.buffer_lock
> mutex being accessed even in external commands were disabled (in which
> case the mutex wouldn't exist).

It aborts both with and without external commands enabled (if you mean the
check_external_commands flag).

> A fix has been committed to CVS (both the 2.x and HEAD branches).  When
> you get a chance, test the new 2.x CVS code and see if it solves the
> problem.

I applied xdata/xsddefault.c rev. 1.58 (or 1.30.2.4) but it doesn't fix the
problem.

	Geert


-------------------------------------------------------------------------
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