kdevelop failing to start

[RISHABH GUPTA]

On Sat, Nov 28, 2015 at 12:08 AM, Milian Wolff <mail at milianw.de> wrote:

> On Dienstag, 24. November 2015 22:29:44 CET RISHABH GUPTA wrote:
> > On Tue, Nov 24, 2015 at 8:18 PM, Milian Wolff <mail at milianw.de> wrote:
> > > On Dienstag, 24. November 2015 19:50:40 CET RISHABH GUPTA wrote:
> > > > On Fri, Nov 13, 2015 at 5:26 PM, RISHABH GUPTA <
> rishabh9511 at gmail.com>
> > > >
> > > > wrote:
> > > > > On Thu, Nov 12, 2015 at 5:47 PM, Milian Wolff <mail at milianw.de>
> wrote:
> > > > >> 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
> > > > >
> > > > > valgrind output
> > > > >
> > > > > http://pastebin.com/Hxcmz7EF
> > > >
> > > > hey,
> > > > could you please suggest  me something to fix this ? will
> reinstalling
> > >
> > > help
> > >
> > > > ?
> > > > If yes, then how should a fresh install be done?
> > > >
> > > > I might be wrong ,but could this be a kdevelop bug ?
> > >
> > > Sorry for the delay.
> > >
> > > The log points at two bugs outside of KDevelop itself, but it doesn't
> show
> > > any
> > > fatal errors. I can reproduce the XCB warning, but not the kcrash one
> on
> > > my
> > > side btw.
> > >
> > > So I guess the real issue is related to the QLockFile that shows up in
> > > your
> > > GDB backtrace. Can you strace kdevelop please:
> > >
> > > strace -e file kdevelop -s test |& grep "\.lock"
> > >
> > > What does this show?
> >
> > http://pastebin.com/nQtUvYm8
> >
> > > Do you have a stale kdeveloprc.lock file in ~/.config/ by
> > > any chance? Who owns that? What does it contain?
> >
> > Yes,owned by me , it's an empty document.
>
> What happens if you remove that file? Can you start KDevelop then?
>

Sorry for  a late reply  .Yes, removing it helped,it's working now .

Thank you


>
> Bye
>
> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20151202/a1926e03/attachment.html>