Bug 124982

Summary:	Starting C/C++ debugger should first rebuild project if sources have changed
Product:	[Applications] kdevelop	Reporter:	Krystof Zacek <krystof.zacek>
Component:	CPP Debugger	Assignee:	kdevelop-bugs-null
Status:	RESOLVED FIXED
Severity:	wishlist
Priority:	NOR
Version:	3.3.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Krystof Zacek 2006-04-05 16:30:17 UTC

Version:           3.3.2 (using KDE 3.5.2, Debian Package 4:3.5.2-2 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.16-1-686

If I change source files and start debugger, the project should be first rebuild before starting debugger.

Currently this does not happen leading to strange debugger behavior - the debugger follows the code from the last build.

There should at least be issued a message like: "The sources changed from the last build. Rebuild the project? Yes/No"

Comment 1 Jens Dagerbo 2006-04-05 19:31:35 UTC

This isn't a bug, it's a wish.

In either case, I think it's implemented on 3.4 branch. Vladimir?

Comment 2 Tim Harper 2006-04-05 20:17:23 UTC

I agree with Krystof, this is borderline wish/bug.  Because the source is rebuilt by default when running the program out of the debugger, the expected behavior is for it to rebuild the source when running it in the debugger.

This may mean also a need to stop any existing debugger front end from running.

Comment 3 Philippe Cloutier 2006-04-23 22:07:45 UTC

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.

Comment 4 Vladimir Prus 2006-05-19 15:28:01 UTC

This is indeed implemented.

Comment 5 Dmitry 2007-08-28 12:52:41 UTC

I've experienced a new problem with this issue. If i've changed the source code and start the debugger answering NO to the 'rebuild' prompt KDevelop freezes.

In fact this may also happen if sources weren't actually changed but KDevelop thinks so.. (i have no idea why, may be it is a separate bug)

My current config is:
    KDE Version  3.4.1 (KDE 3.5.7, Gentoo)
    Operating System  Linux (i686) release 2.6.22-gentoo-r2
    Compiler  Target: i686-pc-linux-gnu