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

[Cgdb-users] Stack and display windows

[Isak J. <is...@hy...>]

Hello!

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

Thanks,
Isak

Re: [Cgdb-users] Question about colors.

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

Hi Ernie,

Unfortunately, this is currently not a feature of CGDB.  All the 
colors are hard coded in the present version.  We're going to be 
reworking the front end soon, and adding configurability to the look 
of the GUI is on the list.

Glad you like it so far. :)

Take Care,
Mike

On Sat, 20 Sep 2003, Ernie Pasveer wrote:

:Hi All,
:
:I quite like using cgdb as my front end to gdb. How can I set the colors of 
:the background and text. I'd rather have white on black.
:
:Cheers,
:
:--ernie
:
:
:
:-------------------------------------------------------
:This sf.net email is sponsored by:ThinkGeek
:Welcome to geek heaven.
:http://thinkgeek.com/sf
:_______________________________________________
:Cgdb-users mailing list
:Cgd...@li...
:https://lists.sourceforge.net/lists/listinfo/cgdb-users

[Cgdb-users] Question about colors.

[Ernie P. <EPa...@ho...>]

Hi All,

I quite like using cgdb as my front end to gdb. How can I set the colors of 
the background and text. I'd rather have white on black.

Cheers,

--ernie

Re: [Cgdb-users] Line number problems.

[Christopher W. <cwe...@k1...>]

On Wed 07/16/2003-06:25:46PM -0400, Bob Rossi wrote:
> 
> String literals now highlight properly.
> You need to grab the latest cvs tree or just wait for the next release.

Wow!  Great support too! :)

Thanks! 

Re: [Cgdb-users] Line number problems.

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

String literals now highlight properly.
You need to grab the latest cvs tree or just wait for the next release.

Bob Rossi

On Wed, Jul 16, 2003 at 02:33:36PM -0400, Bob Rossi wrote:
> Ok, I reproduced the problem.
>=20
> There is a temporary solution until its fixed. Type :set syntax=3Doff in
> the status bar when the file that has the problem is loaded.
>=20
> This bug found 2 error in cgdb. 'set syntax=3Doff' should work in the=20
> $HOME/.cgdb/cgdbrc and it doesn't.
>=20
> The problem will be fixed within a day or two.
>=20
> Thanks for the support!
> Bob Rossi
>=20
> On Wed, Jul 16, 2003 at 12:43:59PM -0400, Christopher Weimann wrote:
> > If a string spans multiple lines cgdb's idea of what
> > line it is on gets completely thrown off.  For example
> > my code includes.
> >=20
> > sprintf( cmd, "SELECT   username,
> >                         password,
> >                         group,
> >                         active
> > 		from users
> > 		where userid=3D%d", userid ) ;=20
> >=20
> > This all winds up on one line in the source view of cgdb
> > but gdb thinks it takes up 6 lines in the source.  Needless
> > to say this really confuses things :)
> >=20
> > I'm using cgdb-0.3.3a.tar.gz downloaded today.
> >=20
> > Other than this little problem I LOVE cgdb.  I have finally=20
> > found something that is textmode and supports vi keystrokes.
> >=20
> > --=20
> > ------------------------------------------------------------
> > Christopher Weimann
> > http://www.k12usa.com
> > K12USA.com Cool Tools for Schools!
> > ------------------------------------------------------------
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.net email is sponsored by: VM Ware
> > With VMware you can run multiple operating systems on a single machine.
> > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
> > same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
> > _______________________________________________
> > Cgdb-users mailing list
> > Cgd...@li...
> > https://lists.sourceforge.net/lists/listinfo/cgdb-users

Re: [Cgdb-users] Line number problems.

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

Ok, I reproduced the problem.

There is a temporary solution until its fixed. Type :set syntax=3Doff in
the status bar when the file that has the problem is loaded.

This bug found 2 error in cgdb. 'set syntax=3Doff' should work in the=20
$HOME/.cgdb/cgdbrc and it doesn't.

The problem will be fixed within a day or two.

Thanks for the support!
Bob Rossi

On Wed, Jul 16, 2003 at 12:43:59PM -0400, Christopher Weimann wrote:
> If a string spans multiple lines cgdb's idea of what
> line it is on gets completely thrown off.  For example
> my code includes.
>=20
> sprintf( cmd, "SELECT   username,
>                         password,
>                         group,
>                         active
> 		from users
> 		where userid=3D%d", userid ) ;=20
>=20
> This all winds up on one line in the source view of cgdb
> but gdb thinks it takes up 6 lines in the source.  Needless
> to say this really confuses things :)
>=20
> I'm using cgdb-0.3.3a.tar.gz downloaded today.
>=20
> Other than this little problem I LOVE cgdb.  I have finally=20
> found something that is textmode and supports vi keystrokes.
>=20
> --=20
> ------------------------------------------------------------
> Christopher Weimann
> http://www.k12usa.com
> K12USA.com Cool Tools for Schools!
> ------------------------------------------------------------
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
> same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
> _______________________________________________
> Cgdb-users mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-users

[Cgdb-users] Line number problems.

[Christopher W. <cs...@k1...>]

If a string spans multiple lines cgdb's idea of what
line it is on gets completely thrown off.  For example
my code includes.

sprintf( cmd, "SELECT   username,
                        password,
                        group,
                        active
		from users
		where userid=%d", userid ) ; 

This all winds up on one line in the source view of cgdb
but gdb thinks it takes up 6 lines in the source.  Needless
to say this really confuses things :)

I'm using cgdb-0.3.3a.tar.gz downloaded today.

Other than this little problem I LOVE cgdb.  I have finally 
found something that is textmode and supports vi keystrokes.

-- 
------------------------------------------------------------
Christopher Weimann
http://www.k12usa.com
K12USA.com Cool Tools for Schools!
------------------------------------------------------------

[Cgdb-users] cgdb & make install because of rlctx_prog

[Bob R. <bob...@co...>]

Hi,

I've committed a patch to rlctx.

It makes it so that cgdb no longer depends on the rlctx_prog program to
have readline support. So, make install is no longer necessary again.

rlctx now only forks to get the functionality needed. The exec is
removed. If any bugs seem to arise related to readline, let me know.

Thanks,
Bob Rossi

Re: [Cgdb-users] cgdb & automake

[Bob R. <bob...@co...>]

On Sat, Apr 26, 2003 at 04:43:01PM -0400, Peter Kovacs wrote:
> I think that's fine.  If, in the future, you wanted to export a single
> library, you could always generate one out of the sublibraries.
>=20
> One of these days I'm seriouly going to finish up that config stuff.
> How do the key bindings work right now?  I'm thinking about adding a
> 'bind' when I create the config file parser.

As of now, libinput receives all input from the tty.
It translates the escape sequences into the keys they represent.

All libinput returns is a regular key or a macro ( CGDB_KEY_UP ).

cgdb uses libinput to get keys. It has hard-coded into it things like

key =3D input_getch();

if ( key =3D=3D CGDB_KEY_UP )
   ...

So, I can imagine that your code will be between libinput and cgdb.

Bobby

>=20
> Peter
>=20
> On Fri, Apr 25, 2003 at 08:30:28PM -0400, Bob Rossi wrote:
> > Hi,
> >=20
> > I re-organized the make system for cgdb/tgdb.
> >=20
> > The new way creates many libraries instead of only one monolithic libtg=
db.a
> >=20
> > This is good because:
> > 1. It physically separates the code into directories.
> > 2. Makes code easier to find and understand
> > 3. It forces units to only rely on lower units
> >=20
> > Its bad because:
> > 1. The user that wants to link to libtgdb has to link to its dependents
> >    The current list is already 5 libraries.=20
> >    ( -lutil -ladt -lannotate-two -lgdbmi -ltgdb )
> > 2. It slows down ./configure;make;make install
> >=20
> > What does everyone think?
>=20
> --=20
> Peter D. Kovacs <pe...@ko...>

Re: [Cgdb-users] cgdb & automake

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

I think that's fine.  If, in the future, you wanted to export a single
library, you could always generate one out of the sublibraries.

One of these days I'm seriouly going to finish up that config stuff.
How do the key bindings work right now?  I'm thinking about adding a
'bind' when I create the config file parser.

Peter

On Fri, Apr 25, 2003 at 08:30:28PM -0400, Bob Rossi wrote:
> Hi,
>=20
> I re-organized the make system for cgdb/tgdb.
>=20
> The new way creates many libraries instead of only one monolithic libtgdb=
.a
>=20
> This is good because:
> 1. It physically separates the code into directories.
> 2. Makes code easier to find and understand
> 3. It forces units to only rely on lower units
>=20
> Its bad because:
> 1. The user that wants to link to libtgdb has to link to its dependents
>    The current list is already 5 libraries.=20
>    ( -lutil -ladt -lannotate-two -lgdbmi -ltgdb )
> 2. It slows down ./configure;make;make install
>=20
> What does everyone think?

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

[Cgdb-users] cgdb & automake

[Bob R. <bob...@co...>]

Hi,

I re-organized the make system for cgdb/tgdb.

The new way creates many libraries instead of only one monolithic libtgdb.a

This is good because:
1. It physically separates the code into directories.
2. Makes code easier to find and understand
3. It forces units to only rely on lower units

Its bad because:
1. The user that wants to link to libtgdb has to link to its dependents
   The current list is already 5 libraries.=20
   ( -lutil -ladt -lannotate-two -lgdbmi -ltgdb )
2. It slows down ./configure;make;make install

What does everyone think?

I strongly like the new system. I personally don't care how long it takes to
compile. The only thing that really bothers me is all of the libraries
the client has to link against.

Thanks,
Bob Rossi

Re: [Cgdb-users] configure problems

[Tim. <ti...@De...>]

> This link is from automake's mailing list.
> It describes the problem you are seeing.
> http://sources.redhat.com/ml/automake/2001-10/msg00066.html
> 
> I am pretty sure it is from upgrading from automake 1.4 to automake 1.5
> or greater. I don't know why it works for me and not you. Let me know if
> you solve the problem and I'll continue looking into it.

Hah, thanks so much for the help.  I laugh because I just figured out what the problem is, and it in no way was automake, or autoconf, or you guys.  I recently updated my CFLAGS and inadvertently I put a newline into the middle of the string.  Yeah I feel pretty stupid.

I apologize for having wasted your time, but I thank you for the effort you did put in.  If it makes you feel any better, that thread that you found did point me in the right direction somehow :o)

And finally... I'd just like to add that I'm happy cgdb is continuing to evolve.  It is without a doubt, my favorite debugger.

Thanks a bunch,

Tim.

Re: [Cgdb-users] configure problems

[Bob R. <bob...@co...>]

On Sun, Apr 20, 2003 at 11:24:55AM -0600, Tim. wrote:
> > I did update the version of automake since version 0.2.1.
> > I have not seen the error you are getting yet.=20
> > Could you please send your OS 'uname -a' and your version of sed.
> >=20
> > I am guessing you are on a Mac, is this true ?
>=20
> No I'm on an intel linux machine.
>=20
> uname -a:
> Linux SpaceDolphin 2.4.20 #2 Thu Mar 27 20:36:05 MST 2003 i686 unknown
>=20
> automake --version:
> automake (GNU automake) 1.7.3
>=20
> autoconf --version:
> autoconf (GNU Autoconf) 2.57
>=20
> sed --version
> GNU sed version 3.02
>=20
> uh oh... I know it's not your guys's fault for sure.  I just tried updati=
ng my sed to the latest version and I got the same problems with its config=
ure script too.
>=20
> I compiled sed on a different machine, and copied the binary over so now =
I'm at 4.0.7, however the problem still exists.
>=20
> It must be with my automake/autoconf.  I too upgraded them recently.  It'=
s a very odd problem because quite a few other configure scripts from other=
 programs work fine.
>=20
> Anyway I will have to track this down. =20
>=20
> Thanks.
>=20

I don't think it is a sed problem. Since I have the same version.

I use
linux 2.4.18
automake 1.7
autoconf 2.57
sed 3.02

This link is from automake's mailing list.
It describes the problem you are seeing.
http://sources.redhat.com/ml/automake/2001-10/msg00066.html

I am pretty sure it is from upgrading from automake 1.4 to automake 1.5
or greater. I don't know why it works for me and not you. Let me know if
you solve the problem and I'll continue looking into it.

Bob Rossi

Re: [Cgdb-users] configure problems

[Tim. <ti...@De...>]

> I did update the version of automake since version 0.2.1.
> I have not seen the error you are getting yet. 
> Could you please send your OS 'uname -a' and your version of sed.
> 
> I am guessing you are on a Mac, is this true ?

No I'm on an intel linux machine.

uname -a:
Linux SpaceDolphin 2.4.20 #2 Thu Mar 27 20:36:05 MST 2003 i686 unknown

automake --version:
automake (GNU automake) 1.7.3

autoconf --version:
autoconf (GNU Autoconf) 2.57

sed --version
GNU sed version 3.02

uh oh... I know it's not your guys's fault for sure.  I just tried updating my sed to the latest version and I got the same problems with its configure script too.

I compiled sed on a different machine, and copied the binary over so now I'm at 4.0.7, however the problem still exists.

It must be with my automake/autoconf.  I too upgraded them recently.  It's a very odd problem because quite a few other configure scripts from other programs work fine.

Anyway I will have to track this down.  

Thanks.

Re: [Cgdb-users] configure problems

[Bob R. <bob...@co...>]

On Sat, Apr 19, 2003 at 11:06:42AM -0600, Tim. wrote:
> Hey guys!
>=20
> I get the following messages while configuring cgdb 0.3.0 (note that I ha=
d no problems with 0.2.1):
>=20
> checking for select... yes
> checking for strdup... yes
> checking for strerror... yes
> configure: creating ./config.status
> config.status: creating Makefile
> sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' comma=
nd
> sed: couldn't write 68 items to {standard output}: Broken pipe
> sed: couldn't write 63 items to {standard output}: Broken pipe
> config.status: creating input/Makefile
> sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' comma=
nd
> sed: couldn't write 18 items to {standard output}: Broken pipe
> config.status: creating input/src/Makefile
> sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' comma=
nd
> sed: couldn't write 42 items to {standard output}: Broken pipe
> sed: Couldn't close {standard output}
> config.status: creating src/Makefile
> sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' comma=
nd
> sed: couldn't write 40 items to {standard output}: Broken pipe
> sed: Couldn't close {standard output}
> config.status: creating tgdb/Makefile
> sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' comma=
nd
> sed: couldn't write 25 items to {standard output}: Broken pipe
> config.status: creating tgdb/annotate-two-src/Makefile
> sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' comma=
nd
> sed: couldn't write 52 items to {standard output}: Broken pipe
> config.status: creating tgdb/gdbmi-src/Makefile
> sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' comma=
nd
> sed: couldn't write 63 items to {standard output}: Broken pipe
> config.status: creating tgdb/lib/Makefile
> sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' comma=
nd
> sed: couldn't write 44 items to {standard output}: Broken pipe
> sed: couldn't write 205 items to {standard output}: Broken pipe
> config.status: creating config.h
> config.status: config.h is unchanged
> config.status: executing depfiles commands
>=20
> Please advise if I am doing something wrong, or if you need more info.
>=20
> Thanks!

I did update the version of automake since version 0.2.1.
I have not seen the error you are getting yet.=20
Could you please send your OS 'uname -a' and your version of sed.

I am guessing you are on a Mac, is this true ?

Thanks,
Bob Rossi

[Cgdb-users] configure problems

[Tim. <ti...@De...>]

Hey guys!

I get the following messages while configuring cgdb 0.3.0 (note that I had no problems with 0.2.1):

checking for select... yes
checking for strdup... yes
checking for strerror... yes
configure: creating ./config.status
config.status: creating Makefile
sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' command
sed: couldn't write 68 items to {standard output}: Broken pipe
sed: couldn't write 63 items to {standard output}: Broken pipe
config.status: creating input/Makefile
sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' command
sed: couldn't write 18 items to {standard output}: Broken pipe
config.status: creating input/src/Makefile
sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' command
sed: couldn't write 42 items to {standard output}: Broken pipe
sed: Couldn't close {standard output}
config.status: creating src/Makefile
sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' command
sed: couldn't write 40 items to {standard output}: Broken pipe
sed: Couldn't close {standard output}
config.status: creating tgdb/Makefile
sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' command
sed: couldn't write 25 items to {standard output}: Broken pipe
config.status: creating tgdb/annotate-two-src/Makefile
sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' command
sed: couldn't write 52 items to {standard output}: Broken pipe
config.status: creating tgdb/gdbmi-src/Makefile
sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' command
sed: couldn't write 63 items to {standard output}: Broken pipe
config.status: creating tgdb/lib/Makefile
sed: file ./confstat26487-23317/subs-2.sed line 7: Unterminated `s' command
sed: couldn't write 44 items to {standard output}: Broken pipe
sed: couldn't write 205 items to {standard output}: Broken pipe
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands

Please advise if I am doing something wrong, or if you need more info.

Thanks!