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

List:       kde-bugs-dist
Subject:    [Bug 265426] KDevelop crash at editing/saving [Kate::TextBuffer::rangesForLine, KateRenderer::decora
From:       Matthew Woehlke <mw_triad () users ! sourceforge ! net>
Date:       2012-12-10 17:26:45
Message-ID: bug-265426-17878-Zgh4xpXrZo () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=265426

--- Comment #50 from Matthew Woehlke <mw_triad@users.sourceforge.net> ---
Another stack trace:

#0  0x000000000061d600 in ?? ()
#1  0x00007fffeaaace5e in Kate::TextBuffer::rangesForLine (this=<optimized
out>, line=76, view=0x8bc00c0, 
    rangesWithAttributeOnly=false) at
/usr/src/debug/kate-4.9.3/part/buffer/katetextbuffer.cpp:820
#2  0x00007fffeab82171 in KateView::updateRangesIn (this=0x8bc00c0,
activationType=
    KTextEditor::Attribute::ActivateMouseIn) at
/usr/src/debug/kate-4.9.3/part/view/kateview.cpp:2845
#3  0x00007fffeab93bb0 in KateViewInternal::mouseMoveEvent (this=0xddc1950,
e=0x7fffffffc870)
    at /usr/src/debug/kate-4.9.3/part/view/kateviewinternal.cpp:2757

I was running in gdb at the time, and can confirm that range->view() is the
problem. (Unfortunately, I tried to 'p range->view()', which borked gdb, so I
no longer have the gdb session to dig further.)

The best way to debug seems to be to make a habit of running kdevelop in gdb
and go about some other work until it crashes. The conditions for triggering
don't seem to be easily reproduced.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]