https://bugs.kde.org/show_bug.cgi?id=386923
--- Comment #8 from Giuseppe Bilotta ---
Sorry for not getting back at you earlier. I just tried with the current git
master, building on debian unstable with all dependencies, and I could not
replicate the deadlock either, neither with nor without the
https://bugs.kde.org/show_bug.cgi?id=386923
--- Comment #9 from Giuseppe Bilotta ---
Ok, so now what I find is that running clinfo under heaptrack causes a
segfault. I can get some more information if I run `heaptrack -d clinfo`.
Sadly, the segmentation fault happens inside the proprietary Intel
https://bugs.kde.org/show_bug.cgi?id=386923
--- Comment #11 from Giuseppe Bilotta ---
I've double-checked against the other platforms, and this time the only one for
which I can reproduce the issue is the proprietary Intel one (in contrast to
the original report, for which I got the
https://bugs.kde.org/show_bug.cgi?id=386923
--- Comment #13 from Giuseppe Bilotta ---
I'm afraid I'm still seeing the same segmentation fault with the Intel
proprietary platform, and only that one.
heaptrack/build [master] $ bin/heaptrack clinfo
heaptrack output will be written
https://bugs.kde.org/show_bug.cgi?id=386923
Bug ID: 386923
Summary: heaptrack stalls forever in LineReader::getLine
Product: Heaptrack
Version: unspecified
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=386923
--- Comment #1 from Giuseppe Bilotta ---
Created attachment 108868
--> https://bugs.kde.org/attachment.cgi?id=108868&action=edit
Thread stack on the debuggee (clinfo) after stalling
The backtrace I showed was only relevant to heaptrack itse
https://bugs.kde.org/show_bug.cgi?id=386923
--- Comment #6 from Giuseppe Bilotta ---
Thanks for the extensive tracking, Milian, I'll find sometime later today to
try the latest git master of heaptrack.
FWIW, I do have the Intel platform available, but I can reproduce the deadlock
by lim
https://bugs.kde.org/show_bug.cgi?id=271308
--- Comment #2 from Giuseppe Bilotta ---
I am still seeing the issue in the latest version of korganizer as shipped
currently by Debian unstable. This is version 4:16.04.3-1; note that the 4: is
the epoch, so this is the KOrganizer part of KDE
