Bug 140674 - Crash when using "S&S C Style" Automatic Indentation mode on doxygen-style /// comment lines
Summary: Crash when using "S&S C Style" Automatic Indentation mode on doxygen-style //...
Status: RESOLVED DUPLICATE of bug 131933
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-26 18:23 UTC by Tim Taylor
Modified: 2007-01-28 11:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Taylor 2007-01-26 18:23:21 UTC
Version:           3.5.4 (using KDE KDE 3.5.4)
Installed from:    Mandriva RPMs
Compiler:          gcc (GCC) 4.1.1 20060724 (prerelease) (4.1.1-3mdk) 
OS:                Linux

This bug concerns a crash in Kate when editing C++ files that contain lines with a doxygen-style triple-slash (///) comment.

To recreate the bug, I do the following:

1. Open Kate (opens a new document)
2. Type "///" on the first line of the document
3. Save the file as "test.cpp" (this tells Kate it is a C++ file?)
4. In Settings->Configure Kate->Editor/Indentation, select "S&S C Style" in the Automatic Indentation dropdown box, and press "OK"
5. Back in the file, position cursor at end of /// line, and press enter/newline
--> Kate crashes!

I get the following debug trace:

Debug trace---------------------------------
(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
 [[previous line repeated 28 times]]
[Thread debugging using libthread_db enabled]
[New Thread -1233557808 (LWP 9011)]
(no debugging symbols found)
 [[previous line repeated 12 times]]
[KCrash handler]
#9  0xb5fbb0e1 in KateTextLine::stringAtPos ()
   from /usr/lib/kde3/libkatepart.so
#10 0xb603eea9 in KateCSAndSIndent::handleDoxygen ()
   from /usr/lib/kde3/libkatepart.so
#11 0xb603f232 in KateCSAndSIndent::processNewline ()
   from /usr/lib/kde3/libkatepart.so
#12 0xb606587a in KateDocument::newLine () from /usr/lib/kde3/libkatepart.so
#13 0xb60724a9 in KateViewInternal::doReturn ()
   from /usr/lib/kde3/libkatepart.so
#14 0xb609c731 in KateView::keyReturn () from /usr/lib/kde3/libkatepart.so
#15 0xb60849ee in KateViewInternal::keyPressEvent ()
   from /usr/lib/kde3/libkatepart.so
#16 0xb606e365 in KateViewInternal::eventFilter ()
   from /usr/lib/kde3/libkatepart.so
#17 0xb70a695c in QObject::activate_filters ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb70a69cb in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb70deedc in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0xb704a037 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0xb704b368 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb777026a in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb6fea8b8 in QETWidget::translateKeyEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb6feb6e5 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb6ffb6aa in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb705fa60 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0xb705f916 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb70499ef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb65cff64 in kdemain () from /usr/lib/libkdeinit_kate.so
#30 0xb7f34813 in kdeinitmain () from /usr/lib/kde3/kate.so
#31 0x0804ee05 in ?? ()
#32 0x0804f732 in ?? ()
#33 0x0804faed in ?? ()
#34 0x080504d3 in ?? ()
#35 0xb67ae75c in __libc_start_main () from /lib/i686/libc.so.6
#36 0x0804baa1 in ?? ()
Comment 1 Anders Lund 2007-01-27 14:48:50 UTC
On Friday 26 January 2007, Tim Taylor wrote:

Can't reproduce.
Comment 2 Dominik Haumann 2007-01-27 15:11:43 UTC
This is most likely a duplicate of bug #131933. If so, this is fixed for KDE 3.5.5.

Tim: Please update KDE (best to 3.5.6) and try again. I will close this report now. If you can still reproduce the crash after having updated KDE, please reopen this report. Thanks.

*** This bug has been marked as a duplicate of 131933 ***
Comment 3 Tim Taylor 2007-01-28 11:20:04 UTC
Hi Dominik, Anders and all,

Thanks for your help.

The bug does indeed look like a duplicate of #131933.  Apologies for that -
I did a search for similar problems before I submitted it, but somehow
missed that one.

I have upgraded to KDE 3.5.6 and the problem has gone away.

Thanks again,

Tim

On 27 Jan 2007 14:11:43 -0000, Dominik Haumann <dhdev@gmx.de> wrote:
[bugs.kde.org quoted mail]
Hi Dominik, Anders and all,<br><br>Thanks for your help.<br><br>The bug does indeed look like a duplicate of #131933.&nbsp; Apologies for that - I did a search for similar problems before I submitted it, but somehow missed that one.
<br><br>I have upgraded to KDE 3.5.6 and the problem has gone away.<br><br>Thanks again,<br><br>Tim<br><br><div><span class="gmail_quote">On 27 Jan 2007 14:11:43 -0000, <b class="gmail_sendername">Dominik Haumann</b> &lt;
<a href="mailto:dhdev@gmx.de">dhdev@gmx.de</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------
<br>You reported the bug, or are watching the reporter.<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=140674">http://bugs.kde.org/show_bug.cgi?id=140674</a><br>dhdev gmx de changed:<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What&nbsp;&nbsp;&nbsp;&nbsp;|Removed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Added
<br>----------------------------------------------------------------------------<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Status|UNCONFIRMED&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |RESOLVED<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Resolution|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|DUPLICATE<br><br><br><br>------- Additional Comments From dhdev gmx de&nbsp;&nbsp;2007-01-27 15:11 -------
<br>This is most likely a duplicate of bug #131933. If so, this is fixed for KDE 3.5.5.<br><br>Tim: Please update KDE (best to 3.5.6) and try again. I will close this report now. If you can still reproduce the crash after having updated KDE, please reopen this report. Thanks.
<br><br>*** This bug has been marked as a duplicate of 131933 ***<br></blockquote></div><br>