Developer forums (C::B DEVELOPMENT STRICTLY!) > Contributions to C::B

C::B and wxWidgets 2.9.5 under Windows

<< < (8/9) > >>

stahta01:

--- Quote from: jens on October 07, 2013, 07:55:14 pm ---
Committed to trunk.

--- End quote ---

Thank you.

Tim S.

oBFusCATed:
Argh.... Running codeblocks-wx29 from within codeblocks makes debugging a simple console application with the second C::B impossible.
The debugger doesn't stop on breakpoints and prints this annoying message:

--- Code: ---During startup program exited with code 1

--- End code ---

Anyone experiencing such issues?
Running codeblocks-wx28 works as expected...

Jenna:

--- Quote from: oBFusCATed on October 11, 2013, 09:55:39 pm ---Argh.... Running codeblocks-wx29 from within codeblocks makes debugging a simple console application with the second C::B impossible.
The debugger doesn't stop on breakpoints and prints this annoying message:

--- Code: ---During startup program exited with code 1

--- End code ---

Anyone experiencing such issues?
Running codeblocks-wx28 works as expected...

--- End quote ---
I just tested it with a console (hello world) application and it works in principal, but I always get the "Detected that the Terminal/Console has been closed. Do you want to stop the debugging session?" annoying dialog.
If I answer with "No", debugging worls as expected, "Yes" stops debugging (also as expected).
I did not (yet) have looked, which of the three conditions (m_stopDebuggerConsoleClosed && m_nConsolePid > 0 && wxKill(m_nConsolePid, wxSIGNONE) != 0 ) is true .

Jenna:
Correction of my previous post:
I get this behaviour with gnome-shell, but not with xterm.
xterm gets closed after the debugging session, gnome-shell stays opened !

oBFusCATed:
Probably this happens, because gnome-shell is running as single process and the instance started by C::B finishes right after it tells the main process what to do. I think there is an option to disable this behaviour.

Navigation

[0] Message Index

[#] Next page

[*] Previous page