[Bug 72076] Output to application view (using external tools) selects lines but will not open a source file at the specified file/line

[Cor van Loos]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
        
http://bugs.kde.org/show_bug.cgi?id=72076        




------- Additional Comments From C_van_Loos Excite com  2004-10-29 13:30 -------
I have also problems when using Lint.

My configuration is slightly different:

- KDevelop v3.3.1.
- Invoking Lint through special target in makefile.
- Lint messages end up in the Messages tab as expected.

Unexpected behaviour is that the error messages (Formatted to look like GCC messages) do not lead to the correct line-number in the corresponding source file.

However when clicking a few lines lower, the editor window does jump.

Example:

cd '/data/pledip' && gmake -k -j1 lint-all
wine c:\\lint\\lint-nt pledip.lnt *.c
PC-lint for C/C++ (NT) Ver. 8.00p, Copyright Gimpel Software 1985-2004 
--- Module: bmpio.c 
--- Module: main.c 
--- Module: pclopt.c 
pclopt.c:628: Error 40 Undeclared identifier 'OPT_END2' 
pclopt.c:628: Error 30 Expected a constant 
pclopt.c:628: Warning 408 Type mismatch with switch expression 
pclopt.c:630: Info 788 enum constant 'OPT_END' not used within defaulted switch 
gmake: *** [lint-all] Error 4
*** Exited with status: 2 ***

When clicking the line starting with 'pclopt.c:630:' KDevelop jumps to the correct file but to line 628 instead of 130. The lines above do not cause any jump. 

When testing larger examples it seems that KDevelop is always at least 4 lines of. So to jump to the location of the error-message on line #1 you have to click on the error message on line #4.

This behaviour is only there when the 'Full compiler output' option is selected.