https://bugs.kde.org/show_bug.cgi?id=407065
Luís Henrique Camargo Quiroz <luis...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luis...@gmail.com
--- Comment #7 from Luís Henrique Camargo Quiroz <luis...@gmail.com> ---
This still happens with KDevelop 5.5.2 (on Debian testing).
For a new and very small project the default configuration is "debug" but the
compilation is not the debug one. I missed lots of time trying to check if I
had configured KDevelop or the launch in wrong ways, even checked in other
machines (where I had to do install, etc). Only when I decided to create a new
configuration as "release" and compiled the project I saw that the executables,
debug and release ones, are the same! And, after that, when I compiled again
the debug version, then the executable was bigger and really with debug
information, and the breakpoints started to work as they should. After... a day
of work :(
Steps to reproduce:
1 - Create a new project, for instance in the category Standard and type
terminal;
2 - I opted not to use a version control system;
3 - A sample/initial main.c appears, I will use it (a "Hello, World!"
classic)
4 - configure a launch for the debug
5 - put a breakpoint in the line that will print the "Hello, World!"
6 - start the debug session
Observed result
The program runs and finishes, without regard to the breakpoint
However, if I create a new configuration for the project (Project/Open
configuration...) of any type (debug or release) then the initial configuration
will bbe compiled as a debug version.
FIX
I noticed, while writing here in the debug tracker, that if I had selected
Project/Configure the selection after the initial project was created, then the
compilation will be correct, with debug information, and breakpoints work
--
You are receiving this mail because:
You are watching all bug changes.
