User forums > Using Code::Blocks
Console app run/debugging for MacOSX
bnilsson:
I will try it.
However, the arguments against /bin/tcsh are strong, so I changed to /bin/bash.
But I will try it with /bin/tcsh, it's easy to switch.
Any progress with the console Terminal debugger?
afb:
--- Quote from: bnilsson on December 04, 2006, 06:41:03 pm ---I will try it.
However, the arguments against /bin/tcsh are strong, so I changed to /bin/bash.
But I will try it with /bin/tcsh, it's easy to switch.
--- End quote ---
Actually there are systems aside from Mac OS X 10.2 that ships with csh as their default shell (PC-BSD did, for instance), so it doesn't hurt to add a feature to support it. Just that I don't like it myself :-)
I'm normally using zsh, so a little choice never hurts.
--- Quote ---Any progress with the console Terminal debugger?
--- End quote ---
I have Build > Run, and I have Debug > Start. What I am looking at for the "console debugger" ?
Did you have some simple steps to test/reproduce the issue, and I'm sure it could be fixed as well.
bnilsson:
What I would ask for is the same behaviour as Run, i.e. to be able to communicate with the app via the Terminal keyboard, but being able to use breakpoints and watches to debug the session.
Right now, l if I start a debug session for a console app, no terminal window appears so I cannot use interactive mode in controlling the application.
bnilsson:
Regarding the above suggestion:
--- Quote ---Would this (new) code work for you:
--- End quote ---
Could you please tell me exactly where to put this in?
I assume it is in compilergcc.cpp, but this file may be revised to the extent that the pattern does not look the same now, since I did not respond right away.
afb:
I'll post a revised snippet, just a little busy with wx 2.8.0 first...
I think the support for Terminal.app and /bin/csh should be able
to go right in, but will update and test with a newer Code::Blocks
Navigation
[0] Message Index
[*] Previous page
Go to full version