Hi Sascha,
On Sun, Jul 24, 2016 at 06:50:38PM +0100, Sascha Steinbiss wrote:
> > 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.
Thanks for the fixes.
> 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.
Any chance to try with Depends: xvfb ?
Kind regards
Andreas.
--
http://fam-tille.de
