[KDE/Mac] The meinproc4 segfault is finally REPRODUCIBLE

René J.V. Bertin rjvbertin at gmail.com
Thu May 7 07:43:36 UTC 2015

On Thursday May 07 2015 13:58:09 Ian Wadham wrote:


>Good workaround.  Are you volunteering?  Unfortunately I have long

Volunteering? Not for the bug hunt, not this one. Once someone has figured out where sh** happens we'll talk again.

>Concurrency is probably not the main issue, but maybe some quirk,

It seems it's the sole cause, though. Would be easy to verify if cmake had some feature to avoid concurrency of a particular command, but I doubt that exists.

>perhaps in XML libs, that does not like simultaneous processing of

This is a very weird concurrency issue I think. We're talking about independent processes causing each other to crash, so there cannot be direct (= interprocess) memory corruption unless meinproc4 uses shared memory. Seems unlikely (why would it) but easy to verify.
I don't know what XML libs are used here, but I also has my doubts that a widely used XML library would contain a bug in this department that somehow never got noticed.
It might be useful to CC the most recent author(s) who has/ve worked on meinproc4 (KDevelop has this handy "git/annotate" feature for that).

>disparate Handbook and manpage doc types.  However, it would not
>hurt much to block all concurrent meinprocs because they usually run
>for only a few seconds each.

That's what I thought too ...




More information about the kde-mac mailing list