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

List:       kdevelop-bugs
Subject:    [Bug 124982] Starting C/C++ debugger should first rebuild project if sources have changed
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2006-04-23 20:07:46
Message-ID: 20060423200746.19177.qmail () ktown ! kde ! org
[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=124982         




------- Additional Comments From cheal hotpop com  2006-04-23 22:07 -------
Hi, I am experiencing this under the same version of kdevelop, the one currently in unstable. I use \
testing, but I took the decision to upgrade kdevelop to unstable because the debugger was too buggy, \
until I realized, after getting assistance from #kdevelop's adymo, that it was just this bug. I agree \
with Tim that the fact that running the program out of the debugger rebuilds it by default makes the \
expected behavior of running in the debugger to rebuild too, but you both seem to be missing what makes \
this really painful: the debugger follows the current code. Until you realize what's wrong, kdevelop \
looks completely nuts. Or if the changes since the last build were minor, it doesn't look completely \
nuts, but still behaves in a way impossible to understand. I wouldn't be surprised if people \
unexperienced with C like me waste hours due to this confusion.

Please upgrade this back to normal.

Note that according to adymo, the bug is fixed for 3.4.


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