cgdb-devel — Development activity -- bug reports, patches, related questions

[Cgdb-devel] Configuration Stuff

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

Okay, I've got my new "configuration" stuff handling all of the :
commands.  It doesn't actually parse an rc file yet (although, since
there are only two variables it controls, ignorecase and shortcut there
isn't much to put in the rc file anyway).

Should I commit what I have now, or wait until I get the keybindings in
place?  Is it okay to have things in CVS that aren't necessarily ready
for release?

- Peter

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

[Cgdb-devel] GDB/MI

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

Hey guys,

I just realized something.  After reading Andrew's responses, as 
well as some of the confusing documentation errors and bug reports 
being posted on the GDB mailing list...  Two things.  First of all, 
Andrew is definitely pulling annotate 2 out for the next release. 
(Regardless of our concerns.)

SO... if GDB 5.4 comes out and MI is as buggy as we think it's going 
to be, we should just detect the version of GDB in CGDB, and if the 
version is 5.4 (or any buggy release), give the user an explanation 
of why their GDB sucks, and that it's not our fault if they're 
experiencing problems.  That's the best I can come up with given how 
inflexible Andrew is being, and the apparent instability of the 
current MI interface.

I have personally given up on trying to talk to the GDB maintainers 
in this regard.  We should continue to go our own way and do what we 
can to support the upcoming whacky releases of GDB.

Mike

[Cgdb-devel] annotatinos

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

Hey guys,

Here is a good history of annotations and its time frame.

http://sources.redhat.com/ml/gdb/2003-02/msg00010.html

Bobby

Re: [Cgdb-devel] Screen-shot

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

On Mon, Feb 03, 2003 at 10:32:24PM -0500, Peter Kovacs wrote:
> Maybe we should change the screenshot on the website to somehow show the
> readline aspects of gdb being used?  And maybe stick some breakpoints
> in there. =20

Some new Screen shots would be great!
I would like a few up there, and a little sentence next to each.
I think I would almost like a tutorial.

>=20
> Whaddya think?
>=20
> Also I noticed that if the source file is too small to fit in the source
> window, its centered.  Is this desired behavior?  I'd personally prefer
> it starting from the top.

Yeah, mike did this on purpose. You'll have to find out why from him.

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


Bobby

[Cgdb-devel] Screen-shot

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

Maybe we should change the screenshot on the website to somehow show the
readline aspects of gdb being used?  And maybe stick some breakpoints
in there. =20

Whaddya think?

Also I noticed that if the source file is too small to fit in the source
window, its centered.  Is this desired behavior?  I'd personally prefer
it starting from the top.

- Peter

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

Re: [Cgdb-devel] CTRL + T

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

That sounds good to me.=20

Bobby

On Sun, Feb 02, 2003 at 05:52:43PM -0500, Peter Kovacs wrote:
> Okay, then basically we need 3 things:
>     1. TTY toggle - shows and hids the TTY window
>     2. TTY focus - if the tty is on the screen, sets the focus.
>     3. restart TTY - create a new pseudo-terminal and issue the tty
>                      command.
>=20
> Does that seem complete?  I'm trying to move away from hard-coded
> key-bindings to a more functional description.
>=20
> - Peter
>=20
> On Sun, Feb 02, 2003 at 05:43:58PM -0500, Bob Rossi wrote:
> > Here's the deal. gdb outputs its data via stdout and the debugged
> > program's date via stdout. So cgdb really has no way of knowing which
> > output is from gdb and which is from the debugged program.=20
> >=20
> > So, in order to distinguish between the 2, cgdb uses gdb's tty feature
> > which tells gdb to use the tty specified for all input and output of
> > the debugged program. That way cgdb reads the debugged programs output
> > via the tty specified and gdb's output via stdout.
> >=20
> > So, the Control-T command actually tells cgdb to open a new tty ( ex.
> > /dev/pts/3). Then it issues the command to gdb ( tty /dev/pts/3 ). So,
> > if something is wrong with the tty, the user can just get another one.
> >=20
> > The T command actually is just a GUI command. It says, I want to look at
> > all the input and output to gdb in a new window. Actually, the only way
> > currently to give input to the program, is through the T command. All
> > it does is says, write all data typed in this window to the tty instead
> > of gdb's stdin.
>=20
> --=20
> Peter D. Kovacs <pe...@ko...>

Re: [Cgdb-devel] CTRL + T

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

Okay, then basically we need 3 things:
    1. TTY toggle - shows and hids the TTY window
    2. TTY focus - if the tty is on the screen, sets the focus.
    3. restart TTY - create a new pseudo-terminal and issue the tty
                     command.

Does that seem complete?  I'm trying to move away from hard-coded
key-bindings to a more functional description.

- Peter

On Sun, Feb 02, 2003 at 05:43:58PM -0500, Bob Rossi wrote:
> Here's the deal. gdb outputs its data via stdout and the debugged
> program's date via stdout. So cgdb really has no way of knowing which
> output is from gdb and which is from the debugged program.=20
>=20
> So, in order to distinguish between the 2, cgdb uses gdb's tty feature
> which tells gdb to use the tty specified for all input and output of
> the debugged program. That way cgdb reads the debugged programs output
> via the tty specified and gdb's output via stdout.
>=20
> So, the Control-T command actually tells cgdb to open a new tty ( ex.
> /dev/pts/3). Then it issues the command to gdb ( tty /dev/pts/3 ). So,
> if something is wrong with the tty, the user can just get another one.
>=20
> The T command actually is just a GUI command. It says, I want to look at
> all the input and output to gdb in a new window. Actually, the only way
> currently to give input to the program, is through the T command. All
> it does is says, write all data typed in this window to the tty instead
> of gdb's stdin.

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

Re: [Cgdb-devel] CTRL + T

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

Here's the deal. gdb outputs its data via stdout and the debugged
program's date via stdout. So cgdb really has no way of knowing which
output is from gdb and which is from the debugged program.=20

So, in order to distinguish between the 2, cgdb uses gdb's tty feature
which tells gdb to use the tty specified for all input and output of
the debugged program. That way cgdb reads the debugged programs output
via the tty specified and gdb's output via stdout.

So, the Control-T command actually tells cgdb to open a new tty ( ex.
/dev/pts/3). Then it issues the command to gdb ( tty /dev/pts/3 ). So,
if something is wrong with the tty, the user can just get another one.

The T command actually is just a GUI command. It says, I want to look at
all the input and output to gdb in a new window. Actually, the only way
currently to give input to the program, is through the T command. All
it does is says, write all data typed in this window to the tty instead
of gdb's stdin.

Is this clear at all? Let me know.

Bobby

On Sun, Feb 02, 2003 at 04:52:23PM -0500, Peter Kovacs wrote:
> Okay, what on earth is the purpose for ctrl+t?  The help documentation
> says:=20
>=20
>     Control-T   -> Opens a new tty for the debugged program
>=20
> But for the life of me I can't tell the difference between this and:
>    =20
>     T           -> Opens a window to give input to the debugged program
>=20
> It seems to allocate a new screen, (I'm not sure if its a brand spanking
> new tty, because its using the same /dev/pts entry).  Can one of these
> disappear?
>=20
> - Peter
>=20
> --=20
> Peter D. Kovacs <pe...@ko...>

[Cgdb-devel] CTRL + T

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

Okay, what on earth is the purpose for ctrl+t?  The help documentation
says:=20

    Control-T   -> Opens a new tty for the debugged program

But for the life of me I can't tell the difference between this and:
   =20
    T           -> Opens a window to give input to the debugged program

It seems to allocate a new screen, (I'm not sure if its a brand spanking
new tty, because its using the same /dev/pts entry).  Can one of these
disappear?

- Peter

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

[Cgdb-devel] Configuration

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

I started adding in some of the configuration source.  Its not
working/integrated yet.=20

config_lexer.l is just a simple tokenizer.  It can recognize some simple
keywords like set, bind, macro (the last two are for future expansion.
:)

configuration.c is basically just stubbed out now.  It does have a list
of the possible commands, as well as configuration variables
(ignorecase, shortcut for now.).

- Peter

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