[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-mac
Subject:    Re: [KDE/Mac] The meinproc4 segfault is finally REPRODUCIBLE
From:       René_J.V. Bertin <rjvbertin () gmail ! com>
Date:       2015-05-07 9:24:46
Message-ID: 1634479.cDDpva82Ei () patux
[Download RAW message or body]

On Thursday May 07 2015 10:36:56 Marko Käning wrote:
Hi

> in this thread and in the related ticket we were discussing this and the
> result was, that it isn't a simple double-use of a cache file. At least
> not the one specified on the command line.

Simple, no. Otherwise Linux would have been affected too, and the bug squashed a long \
time ago.

As I said in an earlier email, the null workaround would be to use a lockfile at the \
start of meinproc4, so that only a single instance is active at a given time. If the \
command takes a cache file argument and that file is created before any work is done, \
that file could serve as the lock (if it's the same for all potentially concurrent \
invocations).

> I just realised that the submitter of that issue still needs to build +docs.
> Perhaps this will produce the crash on his end…

How long does it take to build kmymoney4 +docs? I build my kdelibs4 with a bit more \
than default effort to preserve debugging info, so I actually may stand a better \
chance to produce a useful backtrace. Also, I have a very recent kdelibs4 version \
(4.14.7.16).

R
_______________________________________________
kde-mac@kde.org
List Information: https://mail.kde.org/mailman/listinfo/kde-mac
KDE/Mac Information: http://community.kde.org/Mac


[prev in list] [next in list] [prev in thread] [next in thread]