Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: klight on July 25, 2007, 05:54:41 pm

Title: Debug/Continue fails to launch debugger when no changes detected
Post by: klight on July 25, 2007, 05:54:41 pm
I just built 4320 on WinXP and it appears that the debugger will not start unless the compiler runs.  If the Debug/Continue button is pressed the following text is shown in the Build Log:

Code
Target is up to date.
Nothing to be done.

It also appears that the Debug/Continue button does not always detect that there were changes to the project files as it does not launch the compiler with modified project files present.  This is not always the case, but seems to happen after the Debug/Continue button is pressed (and didn't run) before the modifications were made.

Anyone else seeing similar issues?

*edit* Re-worded the topic title
Title: Re: Debug/Continue fails to launch debugger when no changes detected
Post by: mandrav on July 25, 2007, 07:39:40 pm
Hmm, something related was changed today. I 'll have a look... maybe I missed something.
Title: Re: Debug/Continue fails to launch debugger when no changes detected
Post by: klight on July 25, 2007, 10:18:25 pm
What I've found is that if the Debug/Continue button doesn't start the app, press the Run button (blue "play" button), then immediately exit the app and a debug session will start and appears to function as expected.

Title: Re: Debug/Continue fails to launch debugger when no changes detected
Post by: klight on July 26, 2007, 03:28:43 pm
Rev 4322 is closer to the way it used to be.

Clicking Debug/Continue with modified files fires up the compiler and then the debugger as expected.  This appears to work correctly including pausing/stopping the debugging session.

Clicking Debug/Continue with no modified files appears to still have issues.

Clicking Debug/Continue with no modified files starts the debugger, however the process stops with the line:
Code
Adding file: myprog.exe
and the application is not running.  It seems like it is paused at the beginning of the execution of the application.  All of the debugger buttons are active.  The debug windows (Call stack) window is empty.  Pressing the Debug/Continue button again starts the application.

Pressing the Stop debugger button after the application is running does not "pause" execution, but rather completely stops the debugger.  This only happens if the compiler did not run before starting the debugging session.

Title: Re: Debug/Continue fails to launch debugger when no changes detected
Post by: killerbot on July 26, 2007, 04:27:53 pm
I can confirm this (tested on windows) : this is a nasty one ;-)
Title: Re: Debug/Continue fails to launch debugger when no changes detected
Post by: killerbot on July 26, 2007, 04:31:10 pm
simple console prog from our wizards :

when main.cpp modified --> pressing start debug I get :
Quote
Building to ensure sources are up-to-date
Build succeeded
Selecting target: Debug
Adding source dir: C:\Documents and Settings\ldc\My Documents\CodeBlocks\TestDeleteMe\
Adding source dir: C:\Documents and Settings\ldc\My Documents\CodeBlocks\TestDeleteMe\
Adding file: bin\Debug\TestDeleteMe.exe
Starting debugger: done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb 6.3
Child process PID: 4652
At C:/Documents and Settings/ldc/My Documents/CodeBlocks/TestDeleteMe/main.cpp:7

and we halt at the breakpoint, and then i let it continue --> program finishes and debugging session has ended.

Starting the debug session again now gives :
Quote
Building to ensure sources are up-to-date
Build succeeded
Selecting target: Debug
Adding source dir: C:\Documents and Settings\ldc\My Documents\CodeBlocks\TestDeleteMe\
Adding source dir: C:\Documents and Settings\ldc\My Documents\CodeBlocks\TestDeleteMe\
Adding file: bin\Debug\TestDeleteMe.exe
Starting debugger: done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Build succeeded
Selecting target: Debug
Adding source dir: C:\Documents and Settings\ldc\My Documents\CodeBlocks\TestDeleteMe\
Adding source dir: C:\Documents and Settings\ldc\My Documents\CodeBlocks\TestDeleteMe\
Adding file: bin\Debug\TestDeleteMe.exe
and not stopped at breakpoint, pressing the start debug button again results in the addition in the log of :
Quote
Continuing...
Program exited normally.
Debugger finished with status 0

We can see some things happen once again after the setting of the breakpoints :
Quote
Build succeeded
Selecting target: Debug
Adding source dir: C:\Documents and Settings\ldc\My Documents\CodeBlocks\TestDeleteMe\
Adding source dir: C:\Documents and Settings\ldc\My Documents\CodeBlocks\TestDeleteMe\
Adding file: bin\Debug\TestDeleteMe.exe