[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 146547] New: Debugger tries to cd to obsolete absolute path
From:       Angus <sylvania25 () videotron ! ca>
Date:       2007-06-08 15:33:13
Message-ID: 20070608173312.146547.sylvania25 () videotron ! ca
[Download RAW message or body]

------- 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=146547         
           Summary: Debugger tries to cd to obsolete absolute path
           Product: kdevelop
           Version: 3.4.1
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: sylvania25 videotron ca


Version:           3.4.1 (using KDE KDE 3.5.5KDE 1.2)
Installed from:    SuSE RPMsSuSE RPMs
Compiler:          gcc 4.0.2 
OS:                Linux

My project used to be in /home/angus/myproject_old. Because of versioning I've \
checked out the project in another directory: /home/angus/myproject_new. When I tried \
running the project in debug mode I get:

/home/angus/myproject_old/debug/./src: No such file or directory.

When I turn off the filtering in the gdb window I see that it is because it tried to \
cd into that directory.

A workaround for this is to goto the Project Options|Run Options and force it to use \
the executable with the correct absolute path, which makes selection of the current \
active target meaningless.


[prev in list] [next in list] [prev in thread] [next in thread]