Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Debug/Continue fails to launch debugger when no changes detected

(1/2) > >>

klight:
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.
--- End code ---

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

mandrav:
Hmm, something related was changed today. I 'll have a look... maybe I missed something.

klight:
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.

klight:
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
--- End code ---
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.

killerbot:
I can confirm this (tested on windows) : this is a nasty one ;-)

Navigation

[0] Message Index

[#] Next page