Fwd: Threading problems in WinDBus

[Olivier Hochreutiner]

Attachments did not follow...

---------- Forwarded message ----------
From: Olivier Hochreutiner <olivier.hochreutiner at gmail.com>
Date: 6 juil. 2007 20:46
Subject: Re: Threading problems in WinDBus
To: Ralf Habacker <ralf.habacker at freenet.de>, Peter Kümmel <syntheticpp at gmx.net>
Cc: dbus at lists.freedesktop.org, windbus-devel at lists.sourceforge.net


After a try on Debian 4.0, the same problem exist in the linux distro of D-Bus.


2007/7/6, Olivier Hochreutiner <olivier.hochreutiner at gmail.com>:
> Hi!
>
> As you can see I am still working on D-Bus when I have time :-) and I
> am having problems with the win32 version of WinDBus.
> The problem can be easily reproduced with the echo-server example of
> the c++ binding.
> Just building it and using the "echo-client" program attached allows
> to reproduce the problem.
>
> Every time there is one of the following 4 asserts in the client (but
> maybe others can happen ?):
>
> ----------SNIP----------
> assertion failed "connection->io_path_acquired" file
> "..\..\branches\patched\dbus\dbus-connection.c" line 1082 function
> _dbus_connection_release_io_path
>
> assertion failed "!(connection)->have_connection_lock" file
> "..\..\branches\patched\dbus\dbus-connection.c" line 351 function
> _dbus_connection_lock
>
> assertion failed "(connection)->have_connection_lock" file
> "..\..\branches\patched\dbus\dbus-connection.c" line 362 function
> _dbus_connection_unlock
>
> assertion failed "!(connection)->have_connection_lock" file
> "..\..\branches\patched\dbus\dbus-connection.c" line 2188 function
> check_for_reply_and_update_dispatch_unlocked
> ----------SNIP----------
>
> Note that the function DBus::_init_threading_default() at the
> beginning is just a wrapper to dbus_threads_init_default().
> I didn't have this situation under WinCE so I tried to build the WinCE
> version for Win32 but the problem is the same. I also tried an older
> version from SVN (revision 609 from may 14th) without success.
> I tried to investigate the bug further but I think I am not familiar
> enough with D-Bus internals... What I can say is that it seems to be a
> thread/lock problem (as suggested by the asserts ...)
>
> Having no linux box where I can try, I did not try under that OS.
>
> Any clue of what it can be ?
>
> Thanks,
>
> Olivier
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: echo-proxy.h
Type: text/x-chdr
Size: 2614 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20070706/2649b843/attachment.h 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: EchoProxy.cpp
Type: text/x-c++src
Size: 276 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20070706/2649b843/attachment.cpp 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: EchoProxy.h
Type: text/x-chdr
Size: 279 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20070706/2649b843/attachment-0001.h 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SandBoxDBus.cpp
Type: text/x-c++src
Size: 719 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20070706/2649b843/attachment-0001.cpp