Summary: | crash on start / QTextLine::cursorToX | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Milian Wolff <mail> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | cullmann, elbarto, j__n, mgraesslin, niels, yodor |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Milian Wolff
2012-01-31 10:28:42 UTC
potentially a qt bug but I'll have to investigate in my case maxwidth = 0 (probably the view is not yet shown) and hence .setLineWidth is never called. this seems to be required before calling cursorToX... I can fix the crash for me by checking line.width() != 0 before calling cursorToX. can I push this to kate as a workaround? Yes, if that works around the problem atm, that is ok. Push to 4.8 branch, too, please. I have this exact same bug. kate --version Qt: 4.8.0 KDE Development Platform: 4.8.00 (4.8.0 Kate: 3.8.0 Thread 1 (Thread 0x7f355bac1780 (LWP 8190)): [KCrash Handler] #6 0x00007f3559abedd8 in QTextLine::cursorToX(int*, QTextLine::Edge) const () from /usr/lib/libQtGui.so.4 Any resolution for this bug ? Git commit ee4ffa58cea5798b62c61825c338865cbba82ed8 by Milian Wolff. Committed on 06/02/2012 at 21:58. Pushed by mwolff into branch 'master'. fix crash in QTextLine::cursorToX seems like the above must not be called in Qt 4.8 when the line width is set to zero M +1 -1 part/render/katerenderer.cpp http://commits.kde.org/kate/ee4ffa58cea5798b62c61825c338865cbba82ed8 Git commit cb37d1b2daa09bfa811ffc3962306141f06cb6d1 by Milian Wolff. Committed on 06/02/2012 at 21:58. Pushed by mwolff into branch 'KDE/4.8'. backport from master to 4.8: fix crash in QTextLine::cursorToX seems like the above must not be called in Qt 4.8 when the line width is set to zero M +1 -1 part/render/katerenderer.cpp http://commits.kde.org/kate/cb37d1b2daa09bfa811ffc3962306141f06cb6d1 *** Bug 288583 has been marked as a duplicate of this bug. *** *** Bug 295227 has been marked as a duplicate of this bug. *** *** Bug 295356 has been marked as a duplicate of this bug. *** *** Bug 300432 has been marked as a duplicate of this bug. *** |