cgdb-users

[Cgdb-users] Color problem

[James L. <le...@al...>]

Hi,

I came about cgdb and think it has a lot of potential.
I use vidbg, but development has stop on that project.

Anyway, here is my problem :
I compiled and installed from source and it was ok.
When I ran it in an xterm (white on black background), 
the source window was done quite nicely, with colors 
to the source code. However, the command window is black. 
The text looks to be black also. Can't see the cursor also. 
I know the text is there because it responds to my usual 
gdb commands. However, I just can't read the 
commands nor the output. I tried on konsole (black on white) 
and rxvt and got the same problem.

What is wrong?


James.

Re: [Cgdb-users] Color problem

[Bob R. <bo...@br...>]

> I came about cgdb and think it has a lot of potential.

That's great to hear. CGDB is currently undergoing some major changes,
in the next few months it might actually reach 1.0.

> I use vidbg, but development has stop on that project.
>=20
> Anyway, here is my problem :
> I compiled and installed from source and it was ok.
> When I ran it in an xterm (white on black background),=20
> the source window was done quite nicely, with colors=20
> to the source code. However, the command window is black.=20
> The text looks to be black also. Can't see the cursor also.=20
> I know the text is there because it responds to my usual=20
> gdb commands. However, I just can't read the=20
> commands nor the output. I tried on konsole (black on white)=20
> and rxvt and got the same problem.
>=20
> What is wrong?

I have never seen this problem before. I typically work with an xterm
with white on black. I've also run it on gnome-terminal, cygwin shell,
putty, ...

What is you TERM set to?
Could you tell us the OS?  (uname -a)
The version of GDB that you are using? ( gdb --version )

Also, send us the ~/.tgdb/ directory, that might give me some info.

Mike might have a better idea of what the problem is, but we'll
probably need this info anyways.

Thanks,
Bob Rossi

Re: [Cgdb-users] Color problem

[James L. <le...@al...>]

Bob Rossi [bo...@br...] wrote:
> 
> What is you TERM set to?
> Could you tell us the OS?  (uname -a)
> The version of GDB that you are using? ( gdb --version )

TERM is set to xterm (which is xterm-color really).
I tried a bunch of others (rxvt, xterm-16color, etc)
and they all had the same problem. Then I tried vt100,
and I was able to see the text in the window below. 
The top window has cyan for the logo, and then after 
that, all source is in white (monochrome).
However, the bar dividing the windows is not visible.

OS is RH Linux : 2.4.7-10mntBMsmp #1 SMP
It's an SMP machine (company server).

gdb is 5.2

I'll send the .tgdb directory separately.

Thanks.

James.

Re: [Cgdb-users] Color problem

[Mike M. <mmu...@cs...>]

This is unusual.  First, you should know the current version only
supports black background terminals.  We're currently rewriting to
get a more robust interface, which will eventually be 1.0, but this
is still a few months off.

Anyway, for the problem you're having, what kind of code are you
debugging?  You said the source shows up in white on black, right?
If it is C, C++, or Ada, it should be syntax highlighted in very
eye-pleasing colors. :)  Perhaps this is a bug in CGDB?

Are you doing this over a telnet or rsh/ssh session?  That also
throws some things into the mix, I believe...

Mike

On Wed, 7 Apr 2004, James Lee wrote:

:Bob Rossi [bo...@br...] wrote:
:>
:> What is you TERM set to?
:> Could you tell us the OS?  (uname -a)
:> The version of GDB that you are using? ( gdb --version )
:
:TERM is set to xterm (which is xterm-color really).
:I tried a bunch of others (rxvt, xterm-16color, etc)
:and they all had the same problem. Then I tried vt100,
:and I was able to see the text in the window below.
:The top window has cyan for the logo, and then after
:that, all source is in white (monochrome).
:However, the bar dividing the windows is not visible.
:
:OS is RH Linux : 2.4.7-10mntBMsmp #1 SMP
:It's an SMP machine (company server).
:
:gdb is 5.2
:
:I'll send the .tgdb directory separately.
:
:Thanks.
:
:James.
:
:
:-------------------------------------------------------
:This SF.Net email is sponsored by: IBM Linux Tutorials
:Free Linux tutorial presented by Daniel Robbins, President and CEO of
:GenToo technologies. Learn everything from fundamentals to system
:administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
:_______________________________________________
:Cgdb-users mailing list
:Cgd...@li...
:https://lists.sourceforge.net/lists/listinfo/cgdb-users
:

Re: [Cgdb-users] Color problem

[James L. <le...@al...>]

Mike Mueller [mmu...@cs...] wrote:
> This is unusual.  First, you should know the current version only
> supports black background terminals.  We're currently rewriting to
> get a more robust interface, which will eventually be 1.0, but this
> is still a few months off.

Yes, I know that. I will wait patiently for it. I use plain old
gdb now, vidbg if I really want to see something, or even DDD on
occasions.

> Anyway, for the problem you're having, what kind of code are you
> debugging?  You said the source shows up in white on black, right?
> If it is C, C++, or Ada, it should be syntax highlighted in very
> eye-pleasing colors. :)  Perhaps this is a bug in CGDB?

Yes, I can see the syntax highlighting when TERM is set to a
color terminal (xterm, xtermc, rxvt, etc). The program is in C/C++.
But the problem I described is there from startup of cgdb.
When TERM is set to vt100, then the source code is shown in
white on black. However, there is no current line indicator.

> Are you doing this over a telnet or rsh/ssh session?  That also
> throws some things into the mix, I believe...

My local machine is Sun Sparc running solaris. I rlogin into
the linux machines. I also tried to open an xterm from the linux 
machines back to the local machine and then work on that window.
It has the same problem. I tend to do a lot of these remotely,
so I believe when cgdb does work, I am going to like it.
I went home and installed cgdb on my Debian linux machine, and 
it came up ok.

However, I have no problems with mutt (which also shows color).

Thanks for the reply.


James.

Re: [Cgdb-users] Color problem

[Mike M. <mmu...@cs...>]

> Yes, I know that. I will wait patiently for it. I use plain old
> gdb now, vidbg if I really want to see something, or even DDD on
> occasions.

Ouch... As far as debugging, Bob & I can't imagine using anything other
than CGDB now!  The painfulness of DDD and others is what inspired us to
work on this. :)

> Yes, I can see the syntax highlighting when TERM is set to a
> color terminal (xterm, xtermc, rxvt, etc). The program is in C/C++.
> But the problem I described is there from startup of cgdb.
> When TERM is set to vt100, then the source code is shown in
> white on black. However, there is no current line indicator.

Man... we're both very confused about this.  I'm sorry to say it, but we
haven't come up with a good theory about what could be going wrong with
your setup.  The only thing I'm curious about is what version of ncurses
is installed on the Linux workstation?  I really doubt it's a problem, bu=
t
I'm grasping at straws.

Bob tested it on a pretty similar setup (SunOS telnetting to Linux) today
and did not reproduce the problem.  I have a feeling it would be very har=
d
to recreate...

At least, for now you can use it in black & white with TERM=3Dvt100, righ=
t?=20
Actually, this is a good point, something to keep in mind for our new
version -- the availability of an optional basic monochrome mode would be
a good thing, I think.  That way you'd have the current line indicator,
and the debugger would be totally usable, just not as pretty.

Mike

Re: [Cgdb-users] Color problem

[James L. <le...@al...>]

> Ouch... As far as debugging, Bob & I can't imagine using anything other
> than CGDB now!  The painfulness of DDD and others is what inspired us to
> work on this. :)

That's why I feel that I will like cgdb.

And I finally found the cause of the problem. I have 

    setenv COLORFGBG default

in order to correct some behavior in programs compiled against slang.
Turns out that cgdb has problems when COLORFGBG is set, even when I
set it to "black;white" "white;black", etc. I guess there is a
conflict between this setting and cgdb. Perhaps now you can make it
more robust.

Anyway, now that I get it working, I'm going to give it a full swing.

> At least, for now you can use it in black & white with TERM=vt100, right? 
> Actually, this is a good point, something to keep in mind for our new
> version -- the availability of an optional basic monochrome mode would be
> a good thing, I think.  That way you'd have the current line indicator,
> and the debugger would be totally usable, just not as pretty.

Yes, a monochrome mode is great also. However, I noticed that in mono
(vt100, for example), there are no line numbers and the line indicator
character is not shown. How about just reversing the video on the
current line? 

Thanks once again for a fine job.

James.

Re: [Cgdb-users] Color problem

[Mike M. <mmu...@cs...>]

> That's why I feel that I will like cgdb.

I think you will too. :)

> And I finally found the cause of the problem. I have
>
>     setenv COLORFGBG default
>
> in order to correct some behavior in programs compiled against slang.
> Turns out that cgdb has problems when COLORFGBG is set, even when I
> set it to "black;white" "white;black", etc. I guess there is a
> conflict between this setting and cgdb. Perhaps now you can make it
> more robust.
>
> Anyway, now that I get it working, I'm going to give it a full swing.

Great, glad to hear it!  Good information to have... Let us know if you
have any additional feedback.  Obviously being version 0.4 it is
incomplete, but we find it quite usable as is.

Mike