Hi all,
>> I'll do report but i am looking at source code of gdpc and can't figure out
>> what is wrong i think something about methods is broken.
>
> Usually injecting some printf("DEBUG %s(%i)", __FILE__, __LINE__)
> statements are pretty helpful to detect the location of the problem -
> for sure a debugger might help as well.I have looked at the code as well and some changes in how mutexes are allocated helped to make gdpc start and run the examples mentioned in the README. It does crash every now and then, which may be connected to other locking issues I haven’t fully been able to track down. My suspicion is that it has to do with the move from the deprecated glib mutex functions to their new counterparts in debian/patches/41_glib_deprecated_funcs.patch. I just pushed my changes to git, maybe it helps. Please note that gdpc is a graphical tool; not sure how you would want to do the testing here. The current autopkgtests do not segfault anymore, but fail due to X not being set up in the testbed. Cheers Sascha
signature.asc
Description: Message signed with OpenPGP using GPGMail
