Looks like it's something else...

I have had a lot of trouble figuring out the proper way to shut down the
glib mainloop code.  As soon as I get something that works in one
release, it's broken in another one...

I would guess that's what's at play here...

Nevertheless, I'm not going to commit the change until I fix this other
problem - since the other problem muddies the waters.



On 03/19/2013 09:01 PM, Alan Robertson wrote:
> Problem is - it breaks the Linux tests...  Or at least it seems to...
> Sigh...
>
> ** Message: Count of 'other' pkts received:    1
> GLib (gthread-posix.c): Unexpected error from C library during
> 'pthread_mutex_lock': Invalid argument.  Aborting.
>
> Program received signal SIGABRT, Aborted.
>
> The irony is that I don't use threads at all:  "Life is too short to
> debug threads".
>
> I'll double-check that the previous version passed tests on this OS. 
> It had in the past - but things change...
>
>
>
> On 03/19/2013 06:38 PM, Roger wrote:
>> Here is an export file for changes I made to get a clean cmake on
>> windows.
>>
>> (That's clean cmake, not a clean compile)
>>
>> Roger
>>
>>
>> _______________________________________________
>> Assimilation mailing list - Discovery-Driven Monitoring
>> [email protected]
>> http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation
>> http://assimmon.org/
>

_______________________________________________
Assimilation mailing list - Discovery-Driven Monitoring
[email protected]
http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation
http://assimmon.org/

Reply via email to