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

[Cgdb-devel] is this a bugger?

[beijing_xiaohuo <bei...@12...>]

hi,every developers:


I print a large object's information,and gdb can not show them on one page,so these information is showed through paging。
gdb  prompt me as  below
---Type <return> to continue, or q <return> to quit--


after I choose return, gdb give that prompt again and again ,so I type 'return'  straight forward ,then the  debug session is seem to be disabled


how can I do for this?


Best Regards!

[Cgdb-devel] Mac OS X pre-built cgdb 0.6.6 installer available

[Kyle M. <ma...@gm...>]

For some time now I have been using cgdb on Mac OS X as my preferred  
lightweight gdb gui.  Xcode can be rather clumsy to deal with  
especially if you need to debug something as root, remotely over an  
ssh connection or when there is no Xcode project already set up.

Initially I used MacPorts to build cgdb.  However several of the  
places I was trying to use it didn't have MacPorts installed.  Copying  
a MacPorts-built cgdb binary from one Mac OS X machine to another was  
problematic due to differing architectures and OS versions and the  
need to also copy the readline dynamic library.  Installing MacPorts  
just to get cgdb was also highly inconvenient.

So I started building cgdb myself as a standalone universal binary  
that worked on all Mac OS X versions and architectures I'm likely to  
use.  That version was easily copyable from machine to machine, but  
was slightly inconvenient to install (terminal window, scp the binary  
and man page and sudo install them).

Finally I got tired of that and created a Mac OS X installer package  
(.pkg) in a compressed disk image (.dmg).

The source code to automatically build that installer can be found here:

http://mackyle.github.com/build-cgdb

A pre-built Mac OS X installer for cgdb 0.6.6 that works on Mac OS X  
10.4 and later (both intel and powerpc) can be downloaded directly from:

https://github.com/downloads/mackyle/build-cgdb/cgdb-0.6.6.dmg (340K)

Please feel free to add any of these links to the download page or  
even copy the pre-built .dmg to the source forge downloads area if you  
like.

Regards,

Kyle

[Cgdb-devel] [ cgdb-Bugs-3404527 ] redraw does not happen automatically in tmux

[SourceForge.net <no...@so...>]

Bugs item #3404527, was opened at 2011-09-05 17:49
Message generated for change (Tracker Item Submitted) made by mmmccormic
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=3404527&group_id=72581

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: CGDB
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Matthew McCormick (mmmccormic)
Assigned to: Nobody/Anonymous (nobody)
Summary: redraw does not happen automatically in tmux

Initial Comment:
I don't know if this should be considered a tmux bug or a cgdb bug, but refresh does not occur in a tmux session after a 'next' for instance.

See tmux.sourceforge.net.

Thanks.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=3404527&group_id=72581

Re: [Cgdb-devel] Weird behavior during file-dialog regex search?

[Gilboa D. <gi...@gm...>]

On Thu, 2011-01-27 at 12:44 -0500, Bob Rossi wrote:

> This was fixed in git last night. Give it a try if you'd like to see
> if it works for you. We'll try to get out a bug fix release soon.
> 
> Bob

Hello,

Sorry for the late reply (We had an urgent demo and was far too busy to
do anything useful besides work..)

Can you point me to the commit? If you have no objections, want to
back-port it to 0.6.5 so I can test it and push into Fedora/RHE-stable.

- Gilboa

Re: [Cgdb-devel] [bug-report] when my program called scanf, cgdb failed to return

[liuyond <ia...@gm...>]

On 02/25/2011 07:46 PM, Bob Rossi wrote:
> Hi Justin,
>
> The issue is that you are trying to read from the terminal
> that cgdb is displaying itself on.
>
> You have two options:
>
> - Use the tty window,
>    http://cgdb.sourceforge.net/docs/cgdb-no-split.html#TTY-Window
>    which is kind of awkward and hard to use or
>
> - Run cgdb in a different termainal than the program you
>    are debugging. That involves starting your program in
>    one terminal and then attaching cgdb/gdb to that program
>    in another terminal. This is exactly how i debug cgdb
>    itself. Considering cgdb needs a terminal when it runs.
>
> Hope that's helpful.
>
> Thanks,
> Bob
>
> On Fri, Feb 25, 2011 at 01:57:56PM +0800, liuyond wrote:
>> Hello,
>>
>> I am a new user to cgdb and I like it very mush. However, when I use
>> cgdb to debug a simple program today, it failed to return when my
>> program called scanf to get some information. my program are very
>> simple, it just read a integer from the standard input and then output
>> it. the source code is as follow:
>>
>>     1    #include<stdio.h>
>>     2
>>     3    int main(void)
>>     4    {
>>     5        int n;
>>     6
>>     7        scanf("%d",&n);
>>     8
>>     9        printf("the number you input is: %d\n", n);
>> 10
>> 11        return 0;
>> 12    }
>>
>> I set a breakpoint on line 7, and then type in "run" and "next" command
>> in the gdb window, and then i can input. However it don't return no
>> matter what I type in even when I type in ctrl+d. when I use gdb to
>> debug this program, there is such problem. I don't if there is something
>> wrong with cgdb or something wrong with my system. other more
>> information about my system is:
>>
>> CGDB version: 0.6.5
>> gdb version: GNU gdb (GDB) 7.1-ubuntu
>> gcc version: 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
>> system: ubuntu-10.04
>> kernel:  2.6.36
>>
>> Thanks&   Regards
>>
>> --justin
>>
>>
>> ------------------------------------------------------------------------------
>> Free Software Download: Index, Search&  Analyze Logs and other IT data in
>> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
>> generated by your applications, servers and devices whether physical, virtual
>> or in the cloud. Deliver compliance at lower cost and gain new business
>> insights. http://p.sf.net/sfu/splunk-dev2dev
>> _______________________________________________
>> Cgdb-devel mailing list
>> Cgd...@li...
>> https://lists.sourceforge.net/lists/listinfo/cgdb-devel
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search&  Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> Cgdb-devel mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-devel
Hi Bob,

Thanks for your reply, and now I how to getting input while using cgdb, 
and thanks for your suggestion on debuging too :-)

Thanks,
justin

Re: [Cgdb-devel] [bug-report] when my program called scanf, cgdb failed to return

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

Hi Justin,

The issue is that you are trying to read from the terminal
that cgdb is displaying itself on.

You have two options:

- Use the tty window,
  http://cgdb.sourceforge.net/docs/cgdb-no-split.html#TTY-Window
  which is kind of awkward and hard to use or

- Run cgdb in a different termainal than the program you
  are debugging. That involves starting your program in
  one terminal and then attaching cgdb/gdb to that program
  in another terminal. This is exactly how i debug cgdb
  itself. Considering cgdb needs a terminal when it runs.

Hope that's helpful.

Thanks,
Bob

On Fri, Feb 25, 2011 at 01:57:56PM +0800, liuyond wrote:
> Hello,
> 
> I am a new user to cgdb and I like it very mush. However, when I use
> cgdb to debug a simple program today, it failed to return when my
> program called scanf to get some information. my program are very
> simple, it just read a integer from the standard input and then output
> it. the source code is as follow:
> 
>    1    #include<stdio.h>
>    2
>    3    int main(void)
>    4    {
>    5        int n;
>    6
>    7        scanf("%d",&n);
>    8
>    9        printf("the number you input is: %d\n", n);
> 10
> 11        return 0;
> 12    }
> 
> I set a breakpoint on line 7, and then type in "run" and "next" command
> in the gdb window, and then i can input. However it don't return no
> matter what I type in even when I type in ctrl+d. when I use gdb to
> debug this program, there is such problem. I don't if there is something
> wrong with cgdb or something wrong with my system. other more
> information about my system is:
> 
> CGDB version: 0.6.5
> gdb version: GNU gdb (GDB) 7.1-ubuntu
> gcc version: 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
> system: ubuntu-10.04
> kernel:  2.6.36
> 
> Thanks&  Regards
> 
> --justin
> 
> 
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in 
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business 
> insights. http://p.sf.net/sfu/splunk-dev2dev 
> _______________________________________________
> Cgdb-devel mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-devel

[Cgdb-devel] [bug-report] when my program called scanf, cgdb failed to return

[liuyond <ia...@gm...>]

Hello,

I am a new user to cgdb and I like it very mush. However, when I use
cgdb to debug a simple program today, it failed to return when my
program called scanf to get some information. my program are very
simple, it just read a integer from the standard input and then output
it. the source code is as follow:

   1    #include<stdio.h>
   2
   3    int main(void)
   4    {
   5        int n;
   6
   7        scanf("%d",&n);
   8
   9        printf("the number you input is: %d\n", n);
10
11        return 0;
12    }

I set a breakpoint on line 7, and then type in "run" and "next" command
in the gdb window, and then i can input. However it don't return no
matter what I type in even when I type in ctrl+d. when I use gdb to
debug this program, there is such problem. I don't if there is something
wrong with cgdb or something wrong with my system. other more
information about my system is:

CGDB version: 0.6.5
gdb version: GNU gdb (GDB) 7.1-ubuntu
gcc version: 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
system: ubuntu-10.04
kernel:  2.6.36

Thanks&  Regards

--justin

Re: [Cgdb-devel] Weird behavior during file-dialog regex search?

[Gilboa D. <gi...@gm...>]

On Thu, 2011-01-27 at 12:44 -0500, Bob Rossi wrote:
> On Thu, Nov 11, 2010 at 02:00:53PM +0200, Gilboa Davara wrote:
> > On Wed, 2010-11-10 at 21:54 -0500, Bob Rossi wrote:
> > > On Thu, Oct 28, 2010 at 10:05:15AM +0200, Gilboa Davara wrote:
> > > > Hello,
> > > > 
> > > > I'm trying to solve a bug in Fedora version of CGDB (which I maintain).
> > > > When doing a regular expression search inside the file selection dialog,
> > > > pressing enter does not select the file, instead, it simply jumps to the
> > > > next match.
> > > > The only way to select the first matching file is to press Enter twice.
> > > > 
> > > > By looking at the code (capture_regex in filedlg.c) it seems that
> > > > pressing Enter triggers a search for the next match, instead of simply
> > > > selecting the last highlight.
> > > > Given the fact that cgdb is doing regex-as-you-type search, shouldn't
> > > > cgdb assume that once I press enter, as-you-type search already
> > > > highlighted the last match?
> > > 
> > > OK, that is a really annoying bug, I don't know how I haven't seen
> > > this before. Thanks.
> > > 
> > > I'll have to figure out how to fix this for the next release.
> > 
> > Happy to help.
> > If you could drop me a fix (or even point me at the right direction)
> > I'll push an update for Fedora 12/13/14 and RHEL5.
> 
> This was fixed in git last night. Give it a try if you'd like to see
> if it works for you. We'll try to get out a bug fix release soon.
> 
> Bob

Thanks!

I'll free some time next week to test it.

- Gilboa

[Cgdb-devel] [ cgdb-Bugs-3147517 ] patch to compile cgdb 0.6.5 under FreeBSD 8.2

[SourceForge.net <no...@so...>]

Bugs item #3147517, was opened at 2010-12-29 10:52
Message generated for change (Tracker Item Submitted) made by chmiels
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=3147517&group_id=72581

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: CGDB
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Sebastian Chmielewski (chmiels)
Assigned to: Nobody/Anonymous (nobody)
Summary: patch to compile cgdb 0.6.5 under FreeBSD 8.2

Initial Comment:
while trying to compile cgdb 0.6.5 under FreeBSD 8.2-PRERELEASE I had to add this patch in file pseudo.c:

https://gist.github.com/758376


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=3147517&group_id=72581

Re: [Cgdb-devel] Patch: focus style.

[Mike M. <mi...@su...>]

On Mon, Nov 29, 2010 at 3:37 AM, Gilboa Davara <gi...@gm...> wrote:
> Hello Mike,
>
> :hi SelectedLineNr cterm=reverse seems to be working just fine in serial
> console (checked w/ TERM=vt220, TERM=xterm and TERM=xterm-color).
> It seems to be a safe default option.
>
> - Gilboa

Thanks for checking it out!  In that case, I agree, let's make it the
default behavior.

-- 
Mike Mueller
mi...@su...

Re: [Cgdb-devel] Patch: focus style.

[Gilboa D. <gi...@gm...>]

On Mon, 2010-11-29 at 01:40 -0800, Mike Mueller wrote:
> On Tue, Nov 16, 2010 at 12:12 AM, Gilboa Davara <gi...@gm...> wrote:
> > On Sat, 2010-11-13 at 10:05 -0500, Bob Rossi wrote:
> >> Hi Guys,
> >>
> >> You know, I've also noticed Gilboa's complaint myself quite a
> >> few times. For some reason, I lived with the pain, instead of
> >> fixing it.
> >>
> >> I propose we make this,
> >>    :hi SelectedLineNr cterm=reverse
> >> the default behavior. Any objections?
> >>
> >> Thanks,
> >> Bob
> >>
> >
> > Will cterm have any side effects on say, serial consoles? (Can't test it
> > right now)
> >
> > - Gilboa
> 
> We don't know.  Care to test it?  There is also a 'term' qualifier (in
> addition to 'cterm').  Neither of us do any development over serial lines.
> 

Hello Mike,

:hi SelectedLineNr cterm=reverse seems to be working just fine in serial
console (checked w/ TERM=vt220, TERM=xterm and TERM=xterm-color).
It seems to be a safe default option.

- Gilboa

Re: [Cgdb-devel] Patch: focus style.

[Mike M. <mi...@su...>]

On Tue, Nov 16, 2010 at 12:12 AM, Gilboa Davara <gi...@gm...> wrote:
> On Sat, 2010-11-13 at 10:05 -0500, Bob Rossi wrote:
>> Hi Guys,
>>
>> You know, I've also noticed Gilboa's complaint myself quite a
>> few times. For some reason, I lived with the pain, instead of
>> fixing it.
>>
>> I propose we make this,
>>    :hi SelectedLineNr cterm=reverse
>> the default behavior. Any objections?
>>
>> Thanks,
>> Bob
>>
>
> Will cterm have any side effects on say, serial consoles? (Can't test it
> right now)
>
> - Gilboa

We don't know.  Care to test it?  There is also a 'term' qualifier (in
addition to 'cterm').  Neither of us do any development over serial lines.

-- 
Mike Mueller
mi...@su...

Re: [Cgdb-devel] Patch: focus style.

[Gilboa D. <gi...@gm...>]

On Sat, 2010-11-13 at 10:05 -0500, Bob Rossi wrote:
> Hi Guys,
> 
> You know, I've also noticed Gilboa's complaint myself quite a
> few times. For some reason, I lived with the pain, instead of
> fixing it.
> 
> I propose we make this,
>    :hi SelectedLineNr cterm=reverse
> the default behavior. Any objections?
> 
> Thanks,
> Bob
> 

Will cterm have any side effects on say, serial consoles? (Can't test it
right now)

- Gilboa

Re: [Cgdb-devel] Patch: focus style.

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

Hi Guys,

You know, I've also noticed Gilboa's complaint myself quite a
few times. For some reason, I lived with the pain, instead of
fixing it.

I propose we make this,
   :hi SelectedLineNr cterm=reverse
the default behavior. Any objections?

Thanks,
Bob

On Sat, Nov 13, 2010 at 02:42:29AM -0800, Mike Mueller wrote:
> Hi Gilboa,
> 
> Thanks for submitting the patch.  Although our syntax highlighting
> documentation is probably not perfect, there is in fact a way to
> accomplish this without a patch:
> 
>   :hi SelectedLineNr cterm=reverse
> 
> You could also, for example, make the selected line number red:
> 
>   :hi SelectedLineNr ctermfg=red
> 
> I'm glad you & your coworkers are getting some use out of CGDB. :)
> 
> Mike
> 
> -- 
> Mike Mueller
> mi...@su...
> 
> On Thu, Oct 28, 2010 at 9:01 AM, Gilboa Davara <gi...@gm...> wrote:
> > Hello,
> >
> > While help my co-workers get accustomed to cgdb, I notice that they seem
> > to be unable to detect the current "focus" line when scrolling through
> > the code.
> >
> > Hence I added :set focusstyle cgdbrc option which has two options:
> > - bold: default, current behavior.
> > - highlight: new, current line is inverted (unless it's also the current
> > gdb line)
> >
> > At least according to my coworkers, the "highlight" option it's a major
> > improvement - at least when running under KDE konsole's default color
> > scheme. (Tested also under xterm, seems to work just fine).
> >
> > - Gilboa
> 
> ------------------------------------------------------------------------------
> Centralized Desktop Delivery: Dell and VMware Reference Architecture
> Simplifying enterprise desktop deployment and management using
> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
> client virtualization framework. Read more!
> http://p.sf.net/sfu/dell-eql-dev2dev
> _______________________________________________
> Cgdb-devel mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-devel

Re: [Cgdb-devel] Patch: focus style.

[Mike M. <mi...@su...>]

Hi Gilboa,

Thanks for submitting the patch.  Although our syntax highlighting
documentation is probably not perfect, there is in fact a way to
accomplish this without a patch:

  :hi SelectedLineNr cterm=reverse

You could also, for example, make the selected line number red:

  :hi SelectedLineNr ctermfg=red

I'm glad you & your coworkers are getting some use out of CGDB. :)

Mike

-- 
Mike Mueller
mi...@su...

On Thu, Oct 28, 2010 at 9:01 AM, Gilboa Davara <gi...@gm...> wrote:
> Hello,
>
> While help my co-workers get accustomed to cgdb, I notice that they seem
> to be unable to detect the current "focus" line when scrolling through
> the code.
>
> Hence I added :set focusstyle cgdbrc option which has two options:
> - bold: default, current behavior.
> - highlight: new, current line is inverted (unless it's also the current
> gdb line)
>
> At least according to my coworkers, the "highlight" option it's a major
> improvement - at least when running under KDE konsole's default color
> scheme. (Tested also under xterm, seems to work just fine).
>
> - Gilboa

Re: [Cgdb-devel] Weird behavior during file-dialog regex search?

[Gilboa D. <gi...@gm...>]

On Wed, 2010-11-10 at 21:54 -0500, Bob Rossi wrote:
> On Thu, Oct 28, 2010 at 10:05:15AM +0200, Gilboa Davara wrote:
> > Hello,
> > 
> > I'm trying to solve a bug in Fedora version of CGDB (which I maintain).
> > When doing a regular expression search inside the file selection dialog,
> > pressing enter does not select the file, instead, it simply jumps to the
> > next match.
> > The only way to select the first matching file is to press Enter twice.
> > 
> > By looking at the code (capture_regex in filedlg.c) it seems that
> > pressing Enter triggers a search for the next match, instead of simply
> > selecting the last highlight.
> > Given the fact that cgdb is doing regex-as-you-type search, shouldn't
> > cgdb assume that once I press enter, as-you-type search already
> > highlighted the last match?
> 
> OK, that is a really annoying bug, I don't know how I haven't seen
> this before. Thanks.
> 
> I'll have to figure out how to fix this for the next release.

Happy to help.
If you could drop me a fix (or even point me at the right direction)
I'll push an update for Fedora 12/13/14 and RHEL5.

> 
> Bob

- Gilboa
P.S. Did you have a change to look at the focus patch?

Re: [Cgdb-devel] Weird behavior during file-dialog regex search?

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

On Thu, Oct 28, 2010 at 10:05:15AM +0200, Gilboa Davara wrote:
> Hello,
> 
> I'm trying to solve a bug in Fedora version of CGDB (which I maintain).
> When doing a regular expression search inside the file selection dialog,
> pressing enter does not select the file, instead, it simply jumps to the
> next match.
> The only way to select the first matching file is to press Enter twice.
> 
> By looking at the code (capture_regex in filedlg.c) it seems that
> pressing Enter triggers a search for the next match, instead of simply
> selecting the last highlight.
> Given the fact that cgdb is doing regex-as-you-type search, shouldn't
> cgdb assume that once I press enter, as-you-type search already
> highlighted the last match?

OK, that is a really annoying bug, I don't know how I haven't seen
this before. Thanks.

I'll have to figure out how to fix this for the next release.

Bob

[Cgdb-devel] Patch: focus style.

[Gilboa D. <gi...@gm...>]

Hello,

While help my co-workers get accustomed to cgdb, I notice that they seem
to be unable to detect the current "focus" line when scrolling through
the code.

Hence I added :set focusstyle cgdbrc option which has two options:
- bold: default, current behavior.
- highlight: new, current line is inverted (unless it's also the current
gdb line)

At least according to my coworkers, the "highlight" option it's a major
improvement - at least when running under KDE konsole's default color
scheme. (Tested also under xterm, seems to work just fine).

- Gilboa

[Cgdb-devel] Weird behavior during file-dialog regex search?

[Gilboa D. <gi...@gm...>]

Hello,

I'm trying to solve a bug in Fedora version of CGDB (which I maintain).
When doing a regular expression search inside the file selection dialog,
pressing enter does not select the file, instead, it simply jumps to the
next match.
The only way to select the first matching file is to press Enter twice.

By looking at the code (capture_regex in filedlg.c) it seems that
pressing Enter triggers a search for the next match, instead of simply
selecting the last highlight.
Given the fact that cgdb is doing regex-as-you-type search, shouldn't
cgdb assume that once I press enter, as-you-type search already
highlighted the last match?

Thanks,
- Gilboa

[Cgdb-devel] [ cgdb-Bugs-2936904 ] rline has implicit malloc decl (breaks 64 bit systems)

[SourceForge.net <no...@so...>]

Bugs item #2936904, was opened at 2010-01-22 00:02
Message generated for change (Tracker Item Submitted) made by vapier
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=2936904&group_id=72581

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mike Frysinger (vapier)
Assigned to: Nobody/Anonymous (nobody)
Summary: rline has implicit malloc decl (breaks 64 bit systems)

Initial Comment:
trying to compile 0.6.5 on a 64bit system yields an implicit decl of cgdb_malloc in rline.c, and since it returns a pointer, the value is truncated to 32 bits

i just did:
    sed -i 's:cgdb_malloc:malloc:' various/rline/src/rline.c

but maybe you want to switch the code to use cgdb_malloc completely (add the header / convert the other malloc calls / ...)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=2936904&group_id=72581

[Cgdb-devel] Invalid HTML link in 0.6.5

[Gilboa D. <gi...@gm...>]

Hello Bob,

In the tarball's README, there's a link to the documentation:
http://cgdb.sourceforge.net/documentation.shtml
... Which should be:
http://cgdb.sourceforge.net/documentation.php

- Gilboa

Re: [Cgdb-devel] [Cgdb-announce] CGDB 0.6.5 released

[Gilboa D. <gi...@gm...>]

On Sun, 2010-01-03 at 14:23 -0500, Bob Rossi wrote:
> cgdb-0.6.5 Released
> -------------------

Great news.
Updated builds will be send to Fedora (11, 12, rawhide) and EL5 (via
EPEL).

- Gilboa

[Cgdb-devel] [ cgdb-Bugs-2915568 ] locks using F keys in gdb window

[SourceForge.net <no...@so...>]

Bugs item #2915568, was opened at 2009-12-16 14:06
Message generated for change (Tracker Item Submitted) made by rjleathley
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=2915568&group_id=72581

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: CGDB
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Rob (rjleathley)
Assigned to: Nobody/Anonymous (nobody)
Summary: locks using F keys in gdb window

Initial Comment:
Pressing an F key (eg. F7 finish, F8 next) when the gdb input window has focus causes the application to lock.  Ideally these keys would have the same functionality regardless of mode.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=2915568&group_id=72581

[Cgdb-devel] [ cgdb-Bugs-2864880 ] Can't open pty device on OpenBSD

[SourceForge.net <no...@so...>]

Bugs item #2864880, was opened at 2009-09-23 05:37
Message generated for change (Tracker Item Submitted) made by crouchingturbo
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=2864880&group_id=72581

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: TGDB
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mike Mueller (crouchingturbo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Can't open pty device on OpenBSD

Initial Comment:
Someone trying to use cgdb on OpenBSD reports:

01:04 < powentan> Is there someone using cgdb under OpenBSD 4.4 i386? I got 
                  error messages : "Unable to create PTY pair" and "Unable to 
                  invoke GDB" . Can someone help me to fix it ?

He also said that he has no /dev/ptmx, but he does have a /dev/ptm.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=2864880&group_id=72581

[Cgdb-devel] [ cgdb-Bugs-2855780 ] Documentation files get generated in source tree

[SourceForge.net <no...@so...>]

Bugs item #2855780, was opened at 2009-09-10 00:54
Message generated for change (Tracker Item Submitted) made by crouchingturbo
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=2855780&group_id=72581

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: CGDB
Group: None
Status: Open
Resolution: None
Priority: 1
Private: No
Submitted By: Mike Mueller (crouchingturbo)
Assigned to: Robert Rossi (bobbybrasko)
Summary: Documentation files get generated in source tree

Initial Comment:
When I run 'make' from an external build directory, a few files still get generated in the source tree:

#       doc/cgdb.1
#       doc/cgdb.info
#       doc/stamp-vti
#       doc/version.texi

They should probably appear in the build tree instead.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=2855780&group_id=72581