From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901 Description of problem: Erroneous characters appear in the compiler messages window. This bug also prevents users from simply clicking on entries in the messages window to open source files automatically to the position of the compile error. Version-Release number of selected component (if applicable): kdevelop-2.0.2-2 How reproducible: Always Steps to Reproduce: 1.Open any project in KDevelop (prefereably something that will cause a compile-time error) 2.Run a make or execute 3.Notice the extra characters in front of and after some of the lines. 4.Click on the line that describes a compile error. Because of the leading characters, KDevelop cannot locate the file. Actual Results: ... igmake[3]: Nothing to be done for `all'. 8gmake[3]: Leaving directory `/home/andrew/kdevelop/hello/doc/en' gmake[3]: Entering directory `/home/andrew/kdevelop/hello/doc' Agmake[3]: Nothing to be done for `all-am'. ... notice the extra characters before the word "make" ... ehello.cpp:21: no `int Hello::ello (QWidget *, const char *)' member ... the "e" in front of "hello.cpp" here stops the user from simply clicking on this line and being taken to line 21 of hello.cpp Expected Results: No strange characters in messages window. Clicking on a line that reports an filename, line number, and error should open the editor with the appropriate file and position. Additional info:
It's fixed in kdevelop-2.0.2-3. You will find it in ftp://people.redhat.com/than/7.2 later
RHL is no longer supported. Besides currently available version is 3.2.0 (tons of bugs fixes and new features). I didn't see this bug on 3.2.0. Closing, please reopen if this is still an issue with newer releases.