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

Re: [Cgdb-users] Re: cgdb green arrow to current line of source to be executed

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

On Fri, Jun 17, 2005 at 08:46:40PM -0400, Mike Mueller wrote:
> This is definitely doable, I'll check into it and get back to you.

Hi all,

In case anyone's interested, Mike committed this change to CVS. It will
be a few weeks before I get another release out because I'm extremely
busy and I also want to package readline with CGDB. So Benjamin, if you
want to try that feature right away, try out CVS, it's stable enough to
use.

Here are the features mike told me about, since it's still uncommented.

   :set arrowstyle=3Dshort (default)
      The usual little arrow that we provide
   :set arrowstyle=3Dlong
      An arrow that extends from the line number out to the start of the=20
      given line.  Not too obtrusive but easier to follow.
   :set arrowstyle=3Dhighlight
      No actual arrow drawn.  The line is drawn in black-on-green
      text, so the entire line is highlighted across the screen.  Very
      obtrusive.

The short version of arrowstyle is "as". So, "set as=3Dlong".

Just in case anyone's interested, "long" is my personal favorite and is
going to go into my .cgdb/cgdbrc for now :)

Thanks Mike!
Bobby

Re: [Cgdb-users] Re: cgdb green arrow to current line of source to be executed

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

This is definitely doable, I'll check into it and get back to you.

BTW, you don't have to CC me, I'm on the mailing list. :)

--=20
Mike Mueller
mmu...@cs...

On Fri, Jun 17, 2005 at 08:18:30PM -0400, Bob Rossi wrote:
> On Fri, Jun 17, 2005 at 07:56:53PM -0400, Benjamin Faden wrote:
> > I guess reversing the colors for the line would work.  Anything to
> > make it easier to know which line is currently being executed.  I
> > usually find it hard to line up where markers are pointing to when
> > sourcecode tabbing gets too large.
>=20
> Let me think about this a little bit. I'm sure we can get out another
> release with this feature in it. I was just using mutt, and it
> highlights the line red, by making the backround color red on the
> current line. Maybe I'll look into how that would look.
>=20
> Anyone have any ideas?
>=20
> Mike, you usually have better configuration names than I do. What do you
> think a good config option name for this feature would be?
>=20
> Thanks,
> Bob Rossi

Re: [Cgdb-users] Re: cgdb green arrow to current line of source to be executed

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

On Fri, Jun 17, 2005 at 07:56:53PM -0400, Benjamin Faden wrote:
> I guess reversing the colors for the line would work.  Anything to
> make it easier to know which line is currently being executed.  I
> usually find it hard to line up where markers are pointing to when
> sourcecode tabbing gets too large.

Let me think about this a little bit. I'm sure we can get out another
release with this feature in it. I was just using mutt, and it
highlights the line red, by making the backround color red on the
current line. Maybe I'll look into how that would look.

Anyone have any ideas?

Mike, you usually have better configuration names than I do. What do you
think a good config option name for this feature would be?

Thanks,
Bob Rossi

[Cgdb-users] Re: cgdb green arrow to current line of source to be executed

[Benjamin F. <bf...@gm...>]

I guess reversing the colors for the line would work.  Anything to
make it easier to know which line is currently being executed.  I
usually find it hard to line up where markers are pointing to when
sourcecode tabbing gets too large.

-ben

On 6/17/05, Bob Rossi <bob...@co...> wrote:
> On Fri, Jun 17, 2005 at 06:46:02PM -0400, Benjamin Faden wrote:
> > Hello Bob, Mike, or both,
> >
> > I just recently got cgdb to try and i think it is really useful for
> > when you only have putty to debug.  I think the syntax color still
> > makes it more useful then the gdb tui mode.  I only have one problem
> > with it at the moment, but maybe I'm just missing something.
> >
> > The green arrow that points to the current line of execution in the
> > source window can be quite far away from code thats a couple tabs in
> > making it hard to see which line of code it is pointing to.  Is there
> > a way to have it highlight that entire line instead of just pointing a
> > green arrow to the line?  If not, does this sound like a good idea to
> > you?  I think it would make it much easier to cruise through the
> > source.  If i overlooked an option could you let me know?  Otherwize I
> > think it would be a really neat feature to implement.
>=20
> CGDB currently doesn't do this. Both Mike and I are hesitant to add more
> functionality to CGDB at the moment because the original data structures
> chosen make it very difficult to modify the program.
>=20
> However, your change seems like it could be rather simplistic and it
> will be a long time before I can spare the time necessary to do major
> surgery on CGDB. What did you have in mind as far as highlighting? Would
> you like the line to reverse all the colors? Do you have an example?
>=20
> Thanks,
> Bob Rossi
>

[Cgdb-users] Re: cgdb green arrow to current line of source to be executed

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

On Fri, Jun 17, 2005 at 06:46:02PM -0400, Benjamin Faden wrote:
> Hello Bob, Mike, or both,
> 
> I just recently got cgdb to try and i think it is really useful for
> when you only have putty to debug.  I think the syntax color still
> makes it more useful then the gdb tui mode.  I only have one problem
> with it at the moment, but maybe I'm just missing something.
> 
> The green arrow that points to the current line of execution in the
> source window can be quite far away from code thats a couple tabs in
> making it hard to see which line of code it is pointing to.  Is there
> a way to have it highlight that entire line instead of just pointing a
> green arrow to the line?  If not, does this sound like a good idea to
> you?  I think it would make it much easier to cruise through the
> source.  If i overlooked an option could you let me know?  Otherwize I
> think it would be a really neat feature to implement.

CGDB currently doesn't do this. Both Mike and I are hesitant to add more
functionality to CGDB at the moment because the original data structures
chosen make it very difficult to modify the program.

However, your change seems like it could be rather simplistic and it
will be a long time before I can spare the time necessary to do major
surgery on CGDB. What did you have in mind as far as highlighting? Would 
you like the line to reverse all the colors? Do you have an example?

Thanks,
Bob Rossi

Re: [Cgdb-users] Side by side windows

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

Hi James,

Thanks for the feedback!  The feature you requested is definitely
something we've wanted to do.  The problem is the current design of the
curses front end is not really flexible, so I started to redesign it a
while ago to allow more flexibility, but it didn't go very far (I'm a
slacker).  That's not to say it won't happen, but it will probably be a
while.

Bob is currently putting a lot of effort into supporting the new GDB MI
interface.  When he finishes that, the UI will probably start improving a=
s
he gets time to work on it.

Hopefully you can cope with it the way it is for now. :)  Ultimately the
goal is to have Vim-style split capability, that is, an arbitrary number
of horizontal and vertical splits, so you can rearrange the UI to suit
your environment.  The idea of separating the program output from the GDB
output is a good one, too, and I think we want to do this
(user-configurable).

Thanks again,
Mike

> Hi,
>
> I saw requests for enhancements idea on the website, so
> I thought I will put in one. I'm already very
> productive with this great tool, but some enhancements
> will make it even greater.
>
> Is it difficult to have cgdb run with two windows side
> by side instead of the current top and bottom split? At
> my work place, I have a 1600x1200 monitor, so having it
> side by side allows me to see more of the code (may
> need scrolling keys also if code is too wide). In SUN
> workshop, the output/tgdb window can also be split to
> allow for data to be more cleanly printed on the
> screen, so this is something cgdb can also consider
> having (or having it configurable).
>
> Thanks for this great tool.
>
>
> James.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
> shotput
> a projector? How fast can you ride your desk chair down the office luge
> track?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20
> _______________________________________________
> Cgdb-users mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-users
>

[Cgdb-users] Side by side windows

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

Hi,

I saw requests for enhancements idea on the website, so
I thought I will put in one. I'm already very
productive with this great tool, but some enhancements
will make it even greater.

Is it difficult to have cgdb run with two windows side
by side instead of the current top and bottom split? At
my work place, I have a 1600x1200 monitor, so having it
side by side allows me to see more of the code (may
need scrolling keys also if code is too wide). In SUN
workshop, the output/tgdb window can also be split to
allow for data to be more cleanly printed on the
screen, so this is something cgdb can also consider
having (or having it configurable).

Thanks for this great tool.


James.

Re: [Cgdb-users] building on SUN Solaris

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

On Sat, Oct 02, 2004 at 01:15:13AM -0400, mmu...@cs... wrote:
> Hi James,
>=20
> Thanks for the email.  At the moment our only focus is making cgdb work
> with gdb, but hopefully the framework is in place to support any
> text-based debugger.  If someone (hint hint) wanted to adapt tgdb to work
> with dbx, it should be possible. :)
>=20
> Mike
>=20
> > Hi,
> >
> > I have been using cgdb with Linux, and I would like to use
> > it on SUN Solaris with dbx as well.  Does cgdb support using
> > the dbx debugger or do I have to use gdb?

James,

TGDB is the library within CGDB that does all communication with the
debuggers. The interface for TGDB is currently rediculously simple
because so far, it only really supports communicating with GDB using the
annotate 2 interface. I am currently working on the MI interface to GDB
which will give TGDB a much more powerful interface.

For example, it really only deals with breakpoints, and the current
executing line of the program being debugged. It does only a few other
things.

In order to support dbx, you would have to figure out how dbx
communicates with front ends. If there is no offical way, and front
ends simply speak to it over the CLI interface, then essentially, we
would just have to parse the output of dbx to get the info we need. It
would probably take a month or two of work to get TGDB working with that
interface.

Since I don't currently need that feature (and I'm working on GDB's MI), I'=
m not=20
interested in working on it. If you'd like to take the time to do it, I
can give you all the support you need.

If you can wait a few years, I might get around to it :)

Thanks,
Bob Rossi

Re: [Cgdb-users] building on SUN Solaris

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

Hi James,

Thanks for the email.  At the moment our only focus is making cgdb work
with gdb, but hopefully the framework is in place to support any
text-based debugger.  If someone (hint hint) wanted to adapt tgdb to work
with dbx, it should be possible. :)

Mike

> Hi,
>
> I have been using cgdb with Linux, and I would like to use
> it on SUN Solaris with dbx as well.  Does cgdb support using
> the dbx debugger or do I have to use gdb?
>
>
> Thanks.
>
>
>
> James
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJourna=
l
> Use IT products in your business? Tell us what you think of them. Give =
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Cgdb-users mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-users
>

[Cgdb-users] building on SUN Solaris

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

Hi,

I have been using cgdb with Linux, and I would like to use
it on SUN Solaris with dbx as well.  Does cgdb support using
the dbx debugger or do I have to use gdb?


Thanks.



James

Re: [Cgdb-users] key bindings

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

Hi Mike,

> > 2.  I can't seem to get vi mode in readline in cgdb. Is it
> > allowed? It works in plain gdb.
> 
> I just realized this will not work because CGDB catches <ESC> and does its
> own thing, so you'll never be able to send <ESC> to gdb/readline.  Our
> current use of ESC/i makes it impossible...

Under the current framework, I agree that it will not work
since <esc> is being used in vi to set modes, while cgdb
uses it to jump to source window. However, in your proposed
version 1.0, where window movements uses ctl-w, this could
be ok.

> Thinking about this more generally, if we do what we plan on doing, which
> is that ESC/i does the 'normal' vi command/insert mode switching (but
> doesn't change the focused window), readline's vi-mode won't work either. 
> In either case, we're snagging the <ESC> key before you can send it to
> gdb.

this part, I don't quite understand. What will you be snagging
<esc> for in the new version? Are you planning on allowing
editing in source window?

> James, I hope you're a patient man. :)  These revisions to
> cgdb have been in the works for a while, but we haven't a
> long way to go still.  I honestly have no idea how long
> it'll be before a new version comes out.

Yes, I will be patient. Even now, cgdb 0.50 is very useful
for me already. I'm sure version 1.0 will be great.


Thanks for the work.


James.

Re: [Cgdb-users] key bindings

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

On Wed, Aug 18, 2004 at 09:04:00PM +0000, James Lee wrote:
> > Please try this,
> > :set escdelay=3D10000
> > int the source window. Then, go into the GDB window and try the arrow
> > keys. If it works correct now then I can explain the problem, if it
> > doesn't work, then it is a different, probably worse problem. Please let
> > me know.
>=20
> Yes! It looks like setting this does make it work.
> I guess that means that the program needs to wait
> a bit longer to interpret the escape codes.
>=20
> Thanks, learnt something new about cgdb today.

Great! I'm glad to hear that's the problem. The other problem would have
been much worse :)

You should adjust the value to something reasonable. So that when you
hit <ESC> to go the source window, you don't have to wait for ever. You
could try it at say '60' and then move to '100' if that doesn't work.
The value is in tenths of seconds I believe. You can start CGDB and type
:help to get all of the options. Then search for escdelay to see a
little documentation about it. On the other hand, you could just get
used to hitting <esc><esc> in order to move to the source window.

Anyways, once you get the value that you want, you should add it to your
~/.cgdb/cgdbrc file. Once you do that, you will not have to ever worry
about it again.

Thanks,
Bob Rossi

Re: [Cgdb-users] key bindings

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

> Please try this,
> :set escdelay=10000
> int the source window. Then, go into the GDB window and try the arrow
> keys. If it works correct now then I can explain the problem, if it
> doesn't work, then it is a different, probably worse problem. Please let
> me know.

Yes! It looks like setting this does make it work.
I guess that means that the program needs to wait
a bit longer to interpret the escape codes.

Thanks, learnt something new about cgdb today.


James.

Re: [Cgdb-users] key bindings

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

On Wed, Aug 18, 2004 at 01:35:22AM -0400, Mike Mueller wrote:
> > 2.  I can't seem to get vi mode in readline in cgdb. Is it
> > allowed? It works in plain gdb.
>=20
> I just realized this will not work because CGDB catches <ESC> and does its
> own thing, so you'll never be able to send <ESC> to gdb/readline.  Our
> current use of ESC/i makes it impossible...
>=20
> Thinking about this more generally, if we do what we plan on doing, which
> is that ESC/i does the 'normal' vi command/insert mode switching (but
> doesn't change the focused window), readline's vi-mode won't work either.=
=20
> In either case, we're snagging the <ESC> key before you can send it to
> gdb.

Isn't that going to be true no matter what your escape key is?  Perhaps
you need a meta escape key, like Ctrl-V.  If you want to actually send
an escape to the debugged process, you do a <ctrl-v><esc>, or something
like that.

- Peter

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

Re: [Cgdb-users] key bindings

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

> > This seems like a bug. Normally, when I am in the source
> > window or if I am in the GDB window the page up,page
> > down,home,end, and arrow keys all work the way they are
> > supposed to. If you are in the GDB window and you hit an
> > arrow key, does it move in the correct direction, or does
> > it go up into the source window? If it goes up into the
> > source window, please let me know, this is a bug, and
> > hopefully it can be resolved.
>=20
> The problem I'm talking about happens in the gdb window
> (i.e., I'm trying to scroll the output). It happens most of
> the time, and at other times it works correctly (something
> 70-30 split?). What usually happen is that when I try to use
> arrow keys in the gdb window, instead of paging up and down,
> it jumps into the source window. I'm not sure (you guys
> would know better), but my suspicion is that the escape
> codes from the arrow keys somehow got interpreted as <esc>
> key, thus jumping into the source window.=20

This is one of the two possible problems.

> TERM is set to
> xterm. I'm using this with a SUN sparc machine (and SUN
> keyboard) rsh'ed into linux machines.

Please try this,
:set escdelay=3D10000
int the source window. Then, go into the GDB window and try the arrow
keys. If it works correct now then I can explain the problem, if it
doesn't work, then it is a different, probably worse problem. Please let
me know.

Thanks,
Bob Rossi

Re: [Cgdb-users] key bindings

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

> 2.  I can't seem to get vi mode in readline in cgdb. Is it
> allowed? It works in plain gdb.

I just realized this will not work because CGDB catches <ESC> and does it=
s
own thing, so you'll never be able to send <ESC> to gdb/readline.  Our
current use of ESC/i makes it impossible...

Thinking about this more generally, if we do what we plan on doing, which
is that ESC/i does the 'normal' vi command/insert mode switching (but
doesn't change the focused window), readline's vi-mode won't work either.=
=20
In either case, we're snagging the <ESC> key before you can send it to
gdb.

I definitely see where you're coming from with this.  It seems like in th=
e
context of the gdb window, there should be no command mode for cgdb, it'l=
l
always be in insert mode.  That way if your readline is configured for
vi-mode, you can use it normally.

Bob, do you agree with this assessment?  I believe it doesn't affect our
design at all, but I'm not completely sure.

James, I hope you're a patient man. :)  These revisions to cgdb have been
in the works for a while, but we haven't a long way to go still.  I
honestly have no idea how long it'll be before a new version comes out.

Mike

Re: [Cgdb-users] key bindings

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

Hi Bob,

> This seems like a bug. Normally, when I am in the source
> window or if I am in the GDB window the page up,page
> down,home,end, and arrow keys all work the way they are
> supposed to. If you are in the GDB window and you hit an
> arrow key, does it move in the correct direction, or does
> it go up into the source window? If it goes up into the
> source window, please let me know, this is a bug, and
> hopefully it can be resolved.

The problem I'm talking about happens in the gdb window
(i.e., I'm trying to scroll the output). It happens most of
the time, and at other times it works correctly (something
70-30 split?). What usually happen is that when I try to use
arrow keys in the gdb window, instead of paging up and down,
it jumps into the source window. I'm not sure (you guys
would know better), but my suspicion is that the escape
codes from the arrow keys somehow got interpreted as <esc>
key, thus jumping into the source window. TERM is set to
xterm. I'm using this with a SUN sparc machine (and SUN
keyboard) rsh'ed into linux machines.

> Finally, I have most of the infrastructure in place to get
> the 'map' command working. After Mike finishes his window
> manager, and I finish the new main event loop, 'mapping'
> commands will work. Hopefully this will simplify your use
> of CGDB.

Thanks. I can't wait to use the new features.

Thanks for the great work and quick replies.

James.

Re: [Cgdb-users] key bindings

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

Hi Mike,

> 1.  Bob and I are currently working on an overhaul for cgdb. 
> Unfortunately I haven't been able to put a lot of time into it, but that
> should change soon.  The new concept will be much like you described,
> where window changing is exactly like it is in vim.  C-w j and C-w k will
> work, as well as :split, :vsplit, etc.  I'm currently working on the
> window manager library that will make this possible.  Hopefully you can
> make do with the current version until a beta of this new stuff comes out.
> :)

That sounds really great!

Your replies are so quick. Keep up the good work.


James.

Re: [Cgdb-users] key bindings

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

> Another problem also arises when I=20
> tried to use arrow keys to move up and down the output/debug
> window. Since those keys also send out escape sequences,=20
> I often find the cursor jumping to the source window instead
> of paging, and I cannot page. This is quite limiting for me
> since I often have tons of output to look through.

This seems like a bug. Normally, when I am in the source window or if I
am in the GDB window the page up,page down,home,end, and arrow keys all
work the way they are supposed to. If you are in the GDB window and you
hit an arrow key, does it move in the correct direction, or does it go
up into the source window? If it goes up into the source window, please
let me know, this is a bug, and hopefully it can be resolved.

Finally, I have most of the infrastructure in place to get the 'map'
command working. After Mike finishes his window manager, and I finish
the new main event loop, 'mapping' commands will work. Hopefully this
will simplify your use of CGDB.

Thanks,
Bob Rossi

Re: [Cgdb-users] key bindings

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

Hi James,

Nice to hear from you.  I'm glad cgdb has been useful to you.

1.  Bob and I are currently working on an overhaul for cgdb.=20
Unfortunately I haven't been able to put a lot of time into it, but that
should change soon.  The new concept will be much like you described,
where window changing is exactly like it is in vim.  C-w j and C-w k will
work, as well as :split, :vsplit, etc.  I'm currently working on the
window manager library that will make this possible.  Hopefully you can
make do with the current version until a beta of this new stuff comes out=
.
:)

2.  That's a good question, I'll check into it!

Mike

>
> Hi,
>
> I used cgdb almost everyday at work to do debugging
> whenever I need to debug on linux machines. Having used
> it often, I find some things that perhaps you might want
> to consider, namely key-bindings.
>
> 1.  The keys were supposed to vi-like, but it uses <esc>
> to switch between source, io and debug windows. But <esc> in
> vi changes from insert mode to command mode, which is very
> confusing to me sometimes. I find myself unconsciously
> hitting the <esc> key often! Another problem also arises when I
> tried to use arrow keys to move up and down the output/debug
> window. Since those keys also send out escape sequences,
> I often find the cursor jumping to the source window instead
> of paging, and I cannot page. This is quite limiting for me
> since I often have tons of output to look through.
>
> vim uses ctrl-w j or k to move up or down, which is ok (but
> more keystrokes)
>
>
> 2.  I can't seem to get vi mode in readline in cgdb. Is it
> allowed? It works in plain gdb.
>
> thanks a lot.
>
>
> James.
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Cgdb-users mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-users
>

[Cgdb-users] key bindings

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

Hi,

I used cgdb almost everyday at work to do debugging
whenever I need to debug on linux machines. Having used
it often, I find some things that perhaps you might want
to consider, namely key-bindings.

1.  The keys were supposed to vi-like, but it uses <esc> 
to switch between source, io and debug windows. But <esc> in
vi changes from insert mode to command mode, which is very
confusing to me sometimes. I find myself unconsciously
hitting the <esc> key often! Another problem also arises when I 
tried to use arrow keys to move up and down the output/debug
window. Since those keys also send out escape sequences, 
I often find the cursor jumping to the source window instead
of paging, and I cannot page. This is quite limiting for me
since I often have tons of output to look through.

vim uses ctrl-w j or k to move up or down, which is ok (but
more keystrokes)


2.  I can't seem to get vi mode in readline in cgdb. Is it 
allowed? It works in plain gdb.

thanks a lot.


James.

[Cgdb-users] FASD project: Online survey launched

[<ben...@id...>]

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.

With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.


With many thanks for your participation,
Benno Luthiger


PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________

Re: [Cgdb-users] Any Command History?

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

On Fri, May 07, 2004 at 10:49:27PM +0000, James Lee wrote:
> Bob Rossi [bo...@br...] wrote:
> > At some point (don't know when) we added readline to the TGDB. So,
> > if you start up CGDB, you should be able to do all of the readline
> > commands when typing into the GDB window. This even includes reverse
> > search through the history (^r).
>=20
>=20
> Oops. Turns out it was there and working with ^r. I was just too
> used to using Forte/Workshop's '!' and gdb's back arrow keys.

Glad to hear it works for you. The arrow keys should also work, let me
know if they do not. BTW, let us know of any other improvements that
could be made to make repetitive tasks simpler.

Thanks,
Bob Rossi

Re: [Cgdb-users] Any Command History?

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

Bob Rossi [bo...@br...] wrote:
> At some point (don't know when) we added readline to the TGDB. So,
> if you start up CGDB, you should be able to do all of the readline
> commands when typing into the GDB window. This even includes reverse
> search through the history (^r).


Oops. Turns out it was there and working with ^r. I was just too
used to using Forte/Workshop's '!' and gdb's back arrow keys.

Sorry.


James.

Re: [Cgdb-users] Any Command History?

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

On Fri, May 07, 2004 at 10:16:08PM +0000, James Lee wrote:
> Hi,
>=20
> I've been using cgdb quite a lot.
>=20
> 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.

What version are you using? What system? What version of readline did
you link against?

At some point (don't know when) we added readline to the TGDB. So,
if you start up CGDB, you should be able to do all of the readline
commands when typing into the GDB window. This even includes reverse
search through the history (^r).

Look at $HOME/.tgdb/readline-tgdb.dat. Is the file there?
That's the file that stores the history.

Thanks,
Bob Rossi