cgdb-users — Users -- questions, answers, feature requests

[Cgdb-users] Any Command History?

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

Hi,

I've been using cgdb quite a lot.

is there any command history in cgdb? The docs are very minimal and I
don't seem to find any discussion on it. Often found myself needing to
repeat some command, but don't like having to do a lot of typing (eg.
examining data values). '!' or '!!' doesn't seem to work. Of course,
if there is readline editing, that will be even better.

Thanks. Keep up the good work.


James.

Re: [Cgdb-users] Compiling cgdb on AIX

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

On Fri, May 07, 2004 at 08:39:42AM -0400, Bob Rossi wrote:
> On Fri, May 07, 2004 at 11:08:16AM +0200, Pawel (privately) wrote:
> > Hello!
> >=20
> > I have problems with compiling cgdb on AIX 5.1 (I have read in=20
> > FAQ that cgdb was reported as run on AIX). I have compiled=20
> > necessary GNU libraries such as readline-4.3 and ncurses-5.4.=20
> > So "configure" produces now Makefile. Unfortunately "make"=20
> > command reports that libutil is missing.
> > Where can I find sources of this library? (I heard that this=20
> > library is part of glibc - but glibc does not compile on AIX!)
>=20
> If you already compiled the ncurses and readline packages, that was the
> hardest part. Sorry about the name libutil, we should probably change
> the name to something that more obviously shows that it is part of CGDB.
>=20
> I just reproduced your problem on AIX 4.3 with readline and 4.3 and
> ncurses 5.4. I will fix the problem and release another bug fix release.
> (hopefully today)

Actually, I manually just made the link work. You probably fail with
this command

   $ gcc -g -Wall -I./../../util/include -I./../include
   -I/home/bar/download/readline-4.3/target/include
   -L/home/bar/download/readline-4.3/target/lib
   -I/home/bar/download/ncurses-5.4/include
   -L/home/bar/download/ncurses-5.4/lib   -o getch_driver -L ../../util/src
   getch_driver-getch_driver.o -lutil -lm -lncurses   -lreadline -lcurses


I fails because of the space between the -L and the '../../util/src (5th
line). If you concat them together the link works fine. So, if you are
just dieing to try CGDB, just rerun the command. The rest of the make
should work fine for you. Either way, I'll make a release for you.

Also, on AIX I think I set TERM to dtterm to get color. I don't know if
that's the best one to choose though.

Hope you enjoy CGDB in it's still immature state.

Thanks,
Bob Rossi

Re: [Cgdb-users] Compiling cgdb on AIX

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

On Fri, May 07, 2004 at 11:08:16AM +0200, Pawel (privately) wrote:
> Hello!
>=20
> I have problems with compiling cgdb on AIX 5.1 (I have read in=20
> FAQ that cgdb was reported as run on AIX). I have compiled=20
> necessary GNU libraries such as readline-4.3 and ncurses-5.4.=20
> So "configure" produces now Makefile. Unfortunately "make"=20
> command reports that libutil is missing.
> Where can I find sources of this library? (I heard that this=20
> library is part of glibc - but glibc does not compile on AIX!)

If you already compiled the ncurses and readline packages, that was the
hardest part. Sorry about the name libutil, we should probably change
the name to something that more obviously shows that it is part of CGDB.

I just reproduced your problem on AIX 4.3 with readline and 4.3 and
ncurses 5.4. I will fix the problem and release another bug fix release.
(hopefully today)

Thanks,
Bob Rossi

[Cgdb-users] Compiling cgdb on AIX

[Pawel (privately) <ppr...@wp...>]

Hello!

I have problems with compiling cgdb on AIX 5.1 (I have read in 
FAQ that cgdb was reported as run on AIX). I have compiled 
necessary GNU libraries such as readline-4.3 and ncurses-5.4. 
So "configure" produces now Makefile. Unfortunately "make" 
command reports that libutil is missing.
Where can I find sources of this library? (I heard that this 
library is part of glibc - but glibc does not compile on AIX!)

Thanks in advance.

Regards
Pawel

----------------------------------------------------
Nowość! wyszukiwarka zdjęć, rysunków, grafik
Przekonaj się - czasami słowa nie wystarczą!
http://klik.wp.pl/?adr=http%3A%2F%2Fszukaj.wp.pl%2Fszukaj.html%3Fszukaj%3Dporsche%26lista%3Dm&sid=171

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

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...>]

> 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...>]

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...>]

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...>]

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

[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

[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.

[Cgdb-users] Re: Broken CVS access

[Dmitry S. <Dmi...@ok...>]

On Mon, 17 Nov 2003, Dmitry Semyonov wrote:

> On Mon, 17 Nov 2003, Bob Rossi wrote:
>
> > +++ tgdb_client_interface.c   16 Nov 2003 14:34:41 -0000 1.5
>
> [...]
>
> > Doing a checkout of CVS should have given you this change. If it didn't
> > please let us know. Maybe there is something wrong with our CVS setup.
>
> Yes, I think this is the reason.
>
> $ cvs status tgdb_client_interface.c
> ===================================================================
> File: tgdb_client_interface.c   Status: Up-to-date
>
>    Working revision:    1.4
>    Repository revision: 1.4     /cvsroot/cgdb/cgdb/tgdb/tgdb-base/src/tgdb_client_interface.c,v

Today, I have tried 'cvs update' one more time, and the file (plus some
other ones) were updated at last.


...Bye..Dmitry.

Re: [Cgdb-users] TAB completion

[Dmitry S. <Dmi...@ok...>]

On Mon, 17 Nov 2003, Bob Rossi wrote:

> > > > cgdb-0.3.4 had the completion feature, though it was not very convenient
> > > > -- possible variants were only shown above, but not substituted inside
> > > > the command prompt.
> > >
> > > It was difficult to make the completion work in place. This is a planned
> > > feature for 1.0, although will probably not be done for some time.
> >
> > Well, just for you to know.
> > Inline TAB completion (not only list of prompts) is the main feature I
> > really miss in cgdb. My co-worker even does not want to use cgdb due to
> > lack of this feature. So, may be you'll change the priority.
> > Anyway, thanks for the great tool!
>
> Do you normally use GDB from the command line? or your friend ?

We both use it that way, and also several other people I'm working with.


> As far as I know, there is no front end to GDB that implements that
> feature properly.

May be.
So, what are you waiting for? ;)


...Bye..Dmitry.

Re: [Cgdb-users] TAB completion

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

> > > cgdb-0.3.4 had the completion feature, though it was not very conveni=
ent
> > > -- possible variants were only shown above, but not substituted inside
> > > the command prompt.
> >
> > It was difficult to make the completion work in place. This is a planned
> > feature for 1.0, although will probably not be done for some time.
>=20
> Well, just for you to know.
> Inline TAB completion (not only list of prompts) is the main feature I
> really miss in cgdb. My co-worker even does not want to use cgdb due to
> lack of this feature. So, may be you'll change the priority.
> Anyway, thanks for the great tool!

Do you normally use GDB from the command line? or your friend ?

As far as I know, there is no front end to GDB that implements that
feature properly.


Thanks,
Bob Rossi

Re: [Cgdb-users] TAB completion

[Dmitry S. <Dmi...@ok...>]

Bob,

On Sat, 15 Nov 2003, Bob Rossi wrote:

> > cgdb-0.3.4 had the completion feature, though it was not very convenient
> > -- possible variants were only shown above, but not substituted inside
> > the command prompt.
>
> It was difficult to make the completion work in place. This is a planned
> feature for 1.0, although will probably not be done for some time.

Well, just for you to know.
Inline TAB completion (not only list of prompts) is the main feature I
really miss in cgdb. My co-worker even does not want to use cgdb due to
lack of this feature. So, may be you'll change the priority.
Anyway, thanks for the great tool!


...Bye..Dmitry.

Re: [Cgdb-users] TAB completion

[Dmitry S. <Dmi...@ok...>]

Bob,

On Mon, 17 Nov 2003, Bob Rossi wrote:

> > > If you really like the tab completion feature, check out the latest cvs.

[...]

> You want to make sure that a2_completion_callback is there and not
> a2_command_callback.
>
> $ cvs diff -wu -r 1.4 -r 1.5 tgdb_client_interface.c

[...]

Thanks, TAB completion finally works as in 0.3.4 version.


...Bye..Dmitry.

Broken CVS access (Was: Re: [Cgdb-users] TAB completion)

[Dmitry S. <Dmi...@ok...>]

Bob,

On Mon, 17 Nov 2003, Bob Rossi wrote:

> $ cvs diff -wu -r 1.4 -r 1.5 tgdb_client_interface.c
> Index: tgdb_client_interface.c
> ===================================================================
> RCS file: /cvsroot/cgdb/cgdb/tgdb/tgdb-base/src/tgdb_client_interface.c,v
> retrieving revision 1.4
> retrieving revision 1.5
> diff -w -u -r1.4 -r1.5
> --- tgdb_client_interface.c   24 Oct 2003 01:10:40 -0000 1.4
> +++ tgdb_client_interface.c   16 Nov 2003 14:34:41 -0000 1.5

[...]

> Doing a checkout of CVS should have given you this change. If it didn't
> please let us know. Maybe there is something wrong with our CVS setup.

Yes, I think this is the reason.

$ cvs status tgdb_client_interface.c
===================================================================
File: tgdb_client_interface.c   Status: Up-to-date

   Working revision:    1.4
   Repository revision: 1.4     /cvsroot/cgdb/cgdb/tgdb/tgdb-base/src/tgdb_client_interface.c,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)


...Bye..Dmitry.

Re: [Cgdb-users] TAB completion

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

> > I have fixed the bug in cvs. However, there is no test case yet. I will
> > look into adding the testcase when I get a little more time, probably
> > this week.
> >
> > If you really like the tab completion feature, check out the latest cvs.
>=20
> Thank you, but TAB completion still does not work for me with CVS
> version. Below are the commands I used to install cgdb.

The way you are installing it seems fine. I don't know why CVS isn't
working for you.

The reason tab completion was broken was just a simple error. I rewrote
the interface to the annotate two tgdb code and I called the function
a2_command_callback instead of a2_completion_callback. You should check
to see if you have this patch in your CVS checkout. This should make tab
completion work once again.

You want to make sure that a2_completion_callback is there and not
a2_command_callback.

$ cvs diff -wu -r 1.4 -r 1.5 tgdb_client_interface.c=20
Index: tgdb_client_interface.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/cgdb/cgdb/tgdb/tgdb-base/src/tgdb_client_interface.c,v
retrieving revision 1.4
retrieving revision 1.5
diff -w -u -r1.4 -r1.5
--- tgdb_client_interface.c   24 Oct 2003 01:10:40 -0000 1.4
+++ tgdb_client_interface.c   16 Nov 2003 14:34:41 -0000 1.5
@@ -130,7 +130,7 @@
      /* tgdb_client_change_debugger_prompt */
      a2_change_prompt,
      /* tgdb_client_completion_callback */
-     a2_command_callback,
+     a2_completion_callback,
      /* tgdb_client_return_command*/
      a2_return_client_command,
      /* tgdb_client_modify_breakpoint */


Doing a checkout of CVS should have given you this change. If it didn't
please let us know. Maybe there is something wrong with our CVS setup.

Thanks,
Bob Rossi

Re: [Cgdb-users] TAB completion

[Dmitry S. <Dmi...@ok...>]

Hello Bob.

On Sun, 16 Nov 2003, Bob Rossi wrote:

> I have fixed the bug in cvs. However, there is no test case yet. I will
> look into adding the testcase when I get a little more time, probably
> this week.
>
> If you really like the tab completion feature, check out the latest cvs.

Thank you, but TAB completion still does not work for me with CVS
version. Below are the commands I used to install cgdb.

$ CFLAGS="-Os -march=pentium3 -mfpmath=sse -msse -mmmx" ./configure
--prefix=/usr/local/cgdb-0.4.0-20031116 --disable-dependency-tracking
$ make
$ make install


Then I am entering cgdb, and pressing "he[TAB]".


This is the output of cgdb-0.3.4:

GNU gdb Red Hat Linux (5.1.90CVS-5)
[...]
This GDB was configured as "i386-redhat-linux".
(tgdb) he
help
(tgdb) he


And this is of cgdb-0.4.0-20031116:

GNU gdb Red Hat Linux (5.1.90CVS-5)
[...]
This GDB was configured as "i386-redhat-linux".
(tgdb) he
(tgdb) he


...Bye..Dmitry.

Re: [Cgdb-users] TAB completion

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

> > Does anybody have the same problems with cgdb?
>=20
> Oops. Looks like you found a pretty serious bug.
> I will fix this and add a testcase so that it doesn't happen again.

I have fixed the bug in cvs. However, there is no test case yet. I will
look into adding the testcase when I get a little more time, probably
this week.

If you really like the tab completion feature, check out the latest cvs.

Thanks,
Bob Rossi

Re: [Cgdb-users] TAB completion

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

> I have installed cgdb-0.4.0, and noticed that I cannot use TAB for
> automatic completion from (tgdb) command prompt.
>=20
> cgdb-0.3.4 had the completion feature, though it was not very convenient
> -- possible variants were only shown above, but not substituted inside
> the command prompt.

It was difficult to make the completion work in place. This is a planned
feature for 1.0, although will probably not be done for some time.

> Does anybody have the same problems with cgdb?

Oops. Looks like you found a pretty serious bug.
I will fix this and add a testcase so that it doesn't happen again.

I'll notify you when the problem is fixed.

Thanks,
Bob Rossi

Re: [Cgdb-users] TAB completion

[Peter K. <pe...@ko...>]

Dmitry --

This is a known problem with cgdb.  It is a result of the way the cgdb
interacts with gdb.  I think that the fix is targetted for when the
gdb-mi interface is done.

- Peter

On Sat, Nov 15, 2003 at 10:36:46PM +0300, Dmitry Semyonov wrote:
> Hello all.
>=20
> I have installed cgdb-0.4.0, and noticed that I cannot use TAB for
> automatic completion from (tgdb) command prompt.
>=20
> cgdb-0.3.4 had the completion feature, though it was not very convenient
> -- possible variants were only shown above, but not substituted inside
> the command prompt.
>=20
> Does anybody have the same problems with cgdb?
>=20
>=20
> ...Bye..Dmitry.
>=20
>=20
>=20
> -------------------------------------------------------
> This SF. Net email is sponsored by: GoToMyPC
> GoToMyPC is the fast, easy and secure way to access your computer from
> any Web browser or wireless device. Click here to Try it Free!
> https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=3Dmm/g22lp.tmpl
> _______________________________________________
> Cgdb-users mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-users

--=20
Peter D. Kovacs <pe...@ko...>

[Cgdb-users] TAB completion

[Dmitry S. <Dmi...@ok...>]

Hello all.

I have installed cgdb-0.4.0, and noticed that I cannot use TAB for
automatic completion from (tgdb) command prompt.

cgdb-0.3.4 had the completion feature, though it was not very convenient
-- possible variants were only shown above, but not substituted inside
the command prompt.

Does anybody have the same problems with cgdb?


...Bye..Dmitry.

Re: [Cgdb-users] Stack and display windows

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

> Are there (plans for) stack and display windows in CGDB?

Hi Isak,

I do plan on getting the stack to work in TGDB. We will probably need
someone to hack it into CGDB when I am done. This task is relatively easy
from the TGDB side. However, on the CGDB side, someone would have to
make a new window and display the info in it. Unfortunately, no one has
thought of a user-interface for CGDB when there is more than 3
windows, so that would be another task involved on the CGDB side.
I will add this to the 1.0 proposal right now. :)

The display windows are also a goal for TGDB. However, this task is a
little more difficult and will not be finished for a long time probably.
Also, this model doesn't fit well into a curses application, so I doubt
it will get done for CGDB-1.0. However, after that, anything is
possible.

Thanks,
Bob Rossi