Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: tiwag on June 19, 2005, 06:27:47 pm

Title: can't debug any longer
Post by: tiwag on June 19, 2005, 06:27:47 pm

i don't exactly know since when this happened, but with the last cvs version (about 18th June 2005) i'm definitely no longer able to debug a freshly compiled instance of devel/codeblocks from a running output/codeblocks.

i get an error-messagebox complaining: "Another program instance is already running, aborting"

how can we debug codeblocks with this behaviour ?

ps.
my last backup where this didn't appear is from 29th May 2005

--------------------------------------
wxMSW 2.4.2, Mingw GCC 3.4.2

Title: can't debug any longer
Post by: mandrav on June 19, 2005, 10:23:52 pm

Go to Settings->Environment and disable the single instance option :)

Yiannis.

Title: can't debug any longer
Post by: rickg22 on June 20, 2005, 05:54:32 am

Um, this is an issue I'd like to talk about. When running the debugged version of codeblocks, I happen to change often workspaces (for testing) in the debug version. However, that configuration is saved and I don't want that to happen. So, what should we do with this?

Title: can't debug any longer
Post by: tiwag on June 20, 2005, 05:56:05 am

i didn't know of the existence of the "single instance" option - of course it works now -
thank's Yiannis

Title: can't debug any longer
Post by: tiwag on June 20, 2005, 11:47:33 am

Quote from: rickg22

Um, this is an issue I'd like to talk about. When running the debugged version of codeblocks, I happen to change often workspaces (for testing) in the debug version. However, that configuration is saved and I don't want that to happen. So, what should we do with this?

hi rick, normally i call the debuggee "devel/codeblocks.exe" with a parameter for a debug-project like "path-to/debug_project.cbp"
then you get rid of the default workspace modification.