-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Colored output of the terminal program is displayed without color, with control sequences visible #51
Comments
On Fri, Jul 25, 2014 at 02:37:40PM -0700, yurivict wrote:
In general, cgdb will not make debugging other terminal programs easy. If it's possible, you should start your program from the terminal, and This way your program will have complete access to the terminal and you I hope this is helpful. In the future, I might provide better support Bob Rossi |
I think that cgdb tries to send terminal output to libncurses window, it strips part of the control sequence (0x1b) and this causes this problem. This appears to be a design problem: terminal output shouldn't be sent to the channel that can't accept it. cgdb should use something 'setupterm' call from libncurses, like tmux does. But this is a major redesign. |
On Fri, Jul 25, 2014 at 08:43:36PM -0700, yurivict wrote:
CGDB is going to get lots of major redesigns in the next 6-12 months i Bob Rossi |
On Sun, Jul 27, 2014 at 07:39:19AM -0400, Bob Rossi wrote:
The correct thing to do here, might be to have CGDB require tmux for I'm posting this here so I'll remember this idea when I get back to it. Tmux is really good at terminal emulation. This isn't a problem CGDB Bob Rossi |
this is still an issue, is there a reason this is closed? the problem is with |
I think this is still a problem. |
I have a terminal program that senses if the standard output is a terminal (based on isatty(1)), and automatically prints control sequences when it is a terminal.
The problem is that when run under cgdb, for some reason, isatty(1) returns 'true', but output isn't printed as colored, and control sequences are printed as clear text.
When run under just gdb, output is colored.
This test case demonstrates this problem:
I run on kde4 konsole terminal, if this matters, on FreeBSD 9.
The text was updated successfully, but these errors were encountered: