Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: mariocup on July 12, 2007, 05:11:37 pm

Title: Debugger does not start the correct output file/executable (TARGET_OUTPUT_FILE)
Post by: mariocup on July 12, 2007, 05:11:37 pm

Hi,

if you open different projects in codeblocks the debugger does not start always the correct target output file.

To reproduce the problem just follow these steps and do not perform other actions:
1. Unpack the file switching_projects.zip
2. Add an entry in the menu tools:
e.g. TARGET_OUTPUT_FILE
command: /cmd /c echo
parameter: ${TARGET_OUTPUT_FILE}
option:launch tool in new console.
2. Restart Codeblocks, so that no projects is active or open
3.  Open file Hello Serial.cbp and select Tools-> TARGET_OUTPUT_FILE
The first time everything works fine.

If you open now the project HelloSerInt.cpb it becomes active, but the start of Tools->TARGET_OUTPUT_FILE
return an empty $(TARGET_OUTPUT_FILE). The same behaviour is when you use the debugger.



[attachment deleted by admin]

Title: Re: Debugger does not start the correct output file/executable (TARGET_OUTPUT_FI
Post by: mariocup on July 16, 2007, 01:07:17 pm

Hi,

I made a minimal testprogram for testing this bug and tested it with SVN 4266. Follow the steps of the previous post to reproduce the bug.

[attachment deleted by admin]

Title: Re: Debugger does not start the correct output file/executable (TARGET_OUTPUT_FI
Post by: rhf on July 16, 2007, 01:59:06 pm

Hi,

This may have nothing to do with your problem, but I was getting erratic debugger behavior while experimenting with gcc 4.2 and 4.3.
(I have not tried the debugger with gcc 3.4.5.) Last month, there was a MinGW Snapshot release of gdb-6.6.
After installing this release, everything seems to behave properly.
Good luck.