kdevelop failing to start

[Milian Wolff]

On Donnerstag, 12. November 2015 15:35:17 CET RISHABH GUPTA wrote:
> On Mon, Nov 9, 2015 at 6:47 PM, Milian Wolff <mail at milianw.de> wrote:
> > On Montag, 9. November 2015 14:58:59 CET RISHABH GUPTA wrote:
> > > On irc kevin funk suggested me to remove ~/.cache/kdevduchain , after
> > 
> > this
> > 
> > > instead of getting  a segmentation fault kdevelop gets stuck at 78%
> > > 
> > > output of thread apply all bt
> > > http://pastebin.com/hm2fc727
> > 
> > This looks odd. David, do you have any idea why this could apparently
> > deadlock:
> > 
> > Thread 1 (Thread 0x7fffdd2057c0 (LWP 3778)):
> > #0  0x00007ffff5063c4d in nanosleep () at
> > ../sysdeps/unix/syscall-template.S:
> > 81
> > #1  0x00007ffff57cbd2d in ?? () from
> > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> > #2  0x00007ffff5714ef8 in QThread::msleep(unsigned long) () from /usr/lib/
> > x86_64-linux-gnu/libQt5Core.so.5
> > #3  0x00007ffff58776c0 in QLockFile::tryLock(int) () from /usr/lib/x86_64-
> > linux-gnu/libQt5Core.so.5
> > #4  0x00007ffff67d99f9 in ?? () from /usr/lib/x86_64-linux-gnu/
> > libKF5ConfigCore.so.5
> > #5  0x00007ffff67c4e46 in KConfig::sync() () from
> > /usr/lib/x86_64-linux-gnu/
> > libKF5ConfigCore.so.5
> > #6  0x00007ffff43263fe in KMainWindow::saveAutoSaveSettings() () from
> > /usr/
> > lib/x86_64-linux-gnu/libKF5XmlGui.so.5
> > #7  0x00007ffff4326449 in ?? () from /usr/lib/x86_64-linux-gnu/
> > libKF5XmlGui.so.5
> > #8  0x00007ffff433aaaf in KToolBar::Private::applyCurrentSettings() ()
> > from /
> > usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
> > #9  0x00007ffff433ab27 in KToolBar::applySettings(KConfigGroup const&) ()
> > from
> > /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
> > 
> > Rishabh, did you let kdevelop continue after that, wait a few seconds, and
> > then redid the thread apply all bt? Was it pointing at the same stack
> > frame in
> > thread 1?
> 
> Back trace gave the same information ,nothing changed.
> 
> What is this message ? I never used to get this before ,can it be because
> of this ?
> "warning: Corrupted shared library list: 0x12b3db0 != 0x12a9250"

Never seen that. Could you try to run KDevelop through Valgrind and see if 
that spits out anything useful?

valgrind --track-origins=yes --sms-check=all-non-file kdevelop

Cheers
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20151112/6c9d7dac/attachment.sig>