Bug 56508 - Compile Errors click to wrong source file
Summary: Compile Errors click to wrong source file
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Output Views (show other bugs)
Version: 2.1.3
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
: 60370 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-03-27 19:26 UTC by Roger Hill
Modified: 2003-06-26 10:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Roger Hill 2003-03-27 19:26:46 UTC 
Version:           kdevelop 2.1.3  on kde 3.0.8-8 (Redhat 8.0) (using KDE KDE 3.0.5)
Installed from:    RedHat RPMs
Compiler:          gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)  
OS:          Linux

This similar to bug report 33567, which is marked fixed, closed, but I seem to have got it again on a later release

I normally create kdevelop projects in /home/rch_8/src. If I create a new C++ (terminal) project, called t0, I get the project in /home/rch_8/src/t0, and the sources in /home/rch_8/src/t0/t0.
Assume I have main.cpp, and it compiles with errors, which are reported in the messages window. If I click on an error, or use F4, I get an erro message that /home/rch_8/src/t0/main.cpp does not exist. It should be looking for /home/rch_8/src/t0/t0/main.cpp
Comment 1 Michael Uplawski 2003-03-30 15:27:41 UTC 
Same here: kdevelo 2.1.3 on KDE 3.1.0 (SuSE Upgrade).
Comment 2 Roger Hill 2003-04-02 05:49:39 UTC 
I notice that this only occurs after a Build / Make. It does not occur after a 
Build / Compile File
Comment 3 Amilcar do Carmo Lucas 2003-05-21 11:57:56 UTC 
Isn't it already fixed in CVS?? 
 
HarryF fixed it many times already.
Comment 4 Harald Fernengel 2003-06-06 18:51:20 UTC 
Please try CVS HEAD, should be fixed there.
Comment 5 Amilcar do Carmo Lucas 2003-06-26 10:38:06 UTC 
*** Bug 60370 has been marked as a duplicate of this bug. ***