Bug 138791 - kate crashes after do {} while
Summary: kate crashes after do {} while
Status: RESOLVED DUPLICATE of bug 137157
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-14 07:56 UTC by Marcus Daub
Modified: 2006-12-15 18:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Daub 2006-12-14 07:56:24 UTC 
Version:           2.5.5 (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs
Compiler:          gcc 4.1 (SuSE Linux) 
OS:                Linux

Hello *,

I'm using kate as editor for c-programming. So I have the highlithing-c-syntax.

If I enter:
int main(void)
{
	int a;
	
	do
	{
		int b;
	}
	while

and press after the while the return-key, then kate crashes.
There are other similar occasions but this is one you could reproduce.
My system is openSuSE 10.1 updated with smart and backported kde, so that I have kde 3.5.5 and kate 2.5.5
Thanks in advance for resolving!
With best regards
Marcus Daub
Comment 1 Tommi Tervo 2006-12-14 13:32:00 UTC 
backtrace? Can't reproduce, svn r605k. Possibly dupe of this bug:
http://bugs.kde.org/show_bug.cgi?id=135045
Comment 2 Marcus Daub 2006-12-14 14:42:57 UTC 
The kde-crash-handler doesn't pop up, so I don't know how to make a backtrace. Any hints how I could do?
Maybe crash is the wrong word:
after writing a do {} while loop and pressing (sometimes twice) the return-key directly after while, then kate occupy almost 100% of cpu load and don't react anymore.
The bug appears only if highlighting-c-syntax is on. In normal mode it's ok. It's also ok, if I complete the while like: do {} while(a<5);
kate hangs up only if I press the return-key directly after while.
Comment 3 Dominik Haumann 2006-12-15 09:13:31 UTC 
This looks like a duplicate of bug #137157, can you confirm?
Comment 4 Marcus Daub 2006-12-15 10:10:17 UTC 
Yes it seems to be.
So I'm sorry to open a duplicate bug-report.
How should I proceed?
Comment 5 Leo Savernik 2006-12-15 18:19:15 UTC 
dupe

@Marcus: It should work for the upcoming KDE 3.5.6.

*** This bug has been marked as a duplicate of 137157 ***