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

[Cgdb-users] vertical split screen

[kamou <ka...@gm...>]

Hello everybody,
Is it possible to split the cgdb screens vertically instead of horizontaly ?
with the new widescreen monitors, a lot of space is lost with the actual
screen configuration...
Splitting it vertically (in my point of view) would be way more produtive on
those monitors (better source code visibility + longer gdb screen history)

Regards,
 Ayman Khamouma

Re: [Cgdb-users] Syntax highlight hxx and line highlight

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

Hi Nathan,

On Sun, Oct 04, 2009 at 05:56:04PM +0200, Nathan Huesken wrote:
> I am using cgdb and I like it. To questions I have:
> 
> 1. When the source has the hxx ending, syntax highligting is off. I can
> switch it on, but can this be automated?

Unfortunately, the extensions aren't configurable today, but I can add
.hxx to the hard-coded values for now.  At least that one will work in
our next release.

> 2. Can the current line be highlighted a little more? Light white on
> dark white for the line number is diffictult to see ...

You can configure the highlighting similarly to vim's.  Create a file
called ~/.cgdb/cgdbrc, and add lines like this:

   hi SelectedLineNr ctermbg=Blue ctermfg=White

That would make the currently selected line show up in white against
a blue background, just as an example.  The highlight group names are
documented in cgdb's online help (:help) in section 5.1.

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

[Cgdb-users] Syntax highlight hxx and line highlight

[Nathan H. <cg...@lo...>]

Hi,

I am using cgdb and I like it. To questions I have:

1. When the source has the hxx ending, syntax highligting is off. I can
switch it on, but can this be automated?
2. Can the current line be highlighted a little more? Light white on
dark white for the line number is diffictult to see ...

Thanks!
Nathan 

Re: [Cgdb-users] how to debug mips or arm platform applications

[loody <mi...@gm...>]

Hi:

2009/6/9 loody <mi...@gm...>:
> hi
>
> 2009/6/9 Bob Rossi <bo...@br...>
>>
>> On Sat, Jun 06, 2009 at 11:21:18AM +0800, loody wrote:
>> > Dear all:
>> > Would someone tell me how to debug mips or arm applications by CGDB.
>> > I have cross-toolchain like arm-linux-gdb, but I have no idea how to
>> > embed it with cgdb.
>> > Should I recompile cgdb with arm-linux target or only replace the
>> > build-in gdb with arm-linux-gdb?
>>
>> All I can really tell you is that you should worry about configuring gdb
>> to work properly in the environment that you want. Once you have that
>> working, you can compile cgdb on the arch that you want to run it on.
>> cgdb simply runs gdb on the same machine and communicates with it.
>>
>> I hope that's helpful.
>>
>> Thanks,
>> Bob Rossi
>
> thanks for your help.
> Maybe I don't express my problem very clearly.
> I don't want to run cgdb on my target, suppose arm, directly.
> I just to run cgdb with cross-compiled gdb, like arm-linux-gdb, on my host
> and connect to the gdbserver running on the target.
> I find what I need, -d, which can let me to use cross-gdb instead of native
> gdb on my host.
> appreciate your help and your tool,
> miloody
>From cgdb's website, it says it has the version which can run under cygwin.
But I cannot find where it is located at the choosing package's page.
Would someone tell where I can find it?
appreciate your help,
miloody

Re: [Cgdb-users] how to debug mips or arm platform applications

[loody <mi...@gm...>]

hi

2009/6/9 Bob Rossi <bo...@br...>

> On Sat, Jun 06, 2009 at 11:21:18AM +0800, loody wrote:
> > Dear all:
> > Would someone tell me how to debug mips or arm applications by CGDB.
> > I have cross-toolchain like arm-linux-gdb, but I have no idea how to
> > embed it with cgdb.
> > Should I recompile cgdb with arm-linux target or only replace the
> > build-in gdb with arm-linux-gdb?
>
> All I can really tell you is that you should worry about configuring gdb
> to work properly in the environment that you want. Once you have that
> working, you can compile cgdb on the arch that you want to run it on.
> cgdb simply runs gdb on the same machine and communicates with it.
>
> I hope that's helpful.
>
> Thanks,
> Bob Rossi
>

thanks for your help.
Maybe I don't express my problem very clearly.
I don't want to run cgdb on my target, suppose arm, directly.
I just to run cgdb with cross-compiled gdb, like arm-linux-gdb, on my host
and connect to the gdbserver running on the target.
I find what I need, -d, which can let me to use cross-gdb instead of native
gdb on my host.
appreciate your help and your tool,
miloody

Re: [Cgdb-users] how to debug mips or arm platform applications

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

On Sat, Jun 06, 2009 at 11:21:18AM +0800, loody wrote:
> Dear all:
> Would someone tell me how to debug mips or arm applications by CGDB.
> I have cross-toolchain like arm-linux-gdb, but I have no idea how to
> embed it with cgdb.
> Should I recompile cgdb with arm-linux target or only replace the
> build-in gdb with arm-linux-gdb?

All I can really tell you is that you should worry about configuring gdb
to work properly in the environment that you want. Once you have that
working, you can compile cgdb on the arch that you want to run it on.
cgdb simply runs gdb on the same machine and communicates with it.

I hope that's helpful.

Thanks,
Bob Rossi

[Cgdb-users] how to debug mips or arm platform applications

[loody <mi...@gm...>]

Dear all:
Would someone tell me how to debug mips or arm applications by CGDB.
I have cross-toolchain like arm-linux-gdb, but I have no idea how to
embed it with cgdb.
Should I recompile cgdb with arm-linux target or only replace the
build-in gdb with arm-linux-gdb?
thanks for your help,
miloody

Re: [Cgdb-users] compiling on OS X leopard

[Badi' Abdul-W. <ali...@gm...>]

On May 21, 2008, at 1:23 AM, Horst Schirmeier wrote:

> Sorry, I totally forgot about this request. Is it still an open issue?

Yes and no:
Yes: it still has the same problem compiling.
No: well, it was never really a high priority task for me to to get  
working. I was trying out a lo of different tools at the time. I'll  
probably take another stab (or several) at it once school lets out for  
the summer and post my results.

Thanks for the feedback though. :)

B.A.

Re: [Cgdb-users] compiling on OS X leopard

[Horst S. <sch...@us...>]

On Thu, 15 Nov 2007, Bob Rossi wrote:
> On Thu, Nov 15, 2007 at 08:50:35PM +0100, Horst Schirmeier wrote:
> > On Thu, 15 Nov 2007, Bob Rossi wrote:
> > > Well, we would first need to know how to open a pty on mac os 10.5. Once
> > > we figured that out, we can determine what's going wrong with psuedo.c.
> > > Do you have a /dev/ptmx directory? How about /dev/ptc?
> > 
> > I suggest looking at the location you borrowed that code from in the
> > first place, maybe they already have a solution that works for Leopard
> > (MacOS 10.5). As Cgdb builds fine on 10.4 here, it's very possible that
> > this is a 10.5 only issue.
> > 
> > (MacOS 10.4.11)
> > $ sudo port install cgdb
> > Password:
> > --->  Fetching cgdb
> > --->  Attempting to fetch cgdb-0.6.4.tar.gz from
> > http://downloads.sourceforge.net/cgdb
> > --->  Verifying checksum(s) for cgdb
> > --->  Extracting cgdb
> > --->  Configuring cgdb
> > --->  Building cgdb with target all
> > --->  Staging cgdb into destroot
> > --->  Installing cgdb 0.6.4_0
> > --->  Activating cgdb 0.6.4_0
> > --->  Cleaning cgdb
> 
> Great to see that it works on 10.4. Is it possible that you could send
> us the translation unit for pseudo.c? That way, we could compare the
> two examples. If you can set the CFLAGS, add -save-temps, then after the
> build, psuedo.i should be left around by the compiler.

Sorry, I totally forgot about this request. Is it still an open issue?

-Horst

-- 
PGP-Key 0xD40E0E7A

Re: [Cgdb-users] deprecate shortcut mode

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

On Wed, Mar 26, 2008 at 03:47:47PM +0200, Eugene V. Lyubimkin wrote:
> Bob Rossi wrote:
> > Hi,
> >
> > I'm considering deprecating shortcut mode in the next release of cgdb.
> >
> > I get complaints on a monthly basis that when in shortcut mode, 'n'
> > is 'next' in gdb, but it collides with the next search functionality.
> >
> > So, I'm thinking this is a flaw in the cgdb interface, all it does is
> > confuse users. Currently, when in the source window,
> >   F5 triggers the GDB 'run' command.
> >   F6 triggers the GDB 'continue' command.
> >   F7 triggers the GDB 'finish' command.
> >   F8 triggers the GDB 'next' command.
> >   F10 triggers the GDB 'step' command.
> > These are all the shortcut options that you get while in shortcut mode.
> > So, if I remove the shortcut mode option, you can still get all of the
> > same functionality via the F keys.
> >
> > However, if a user is absolutely addicted to the shortcut mode, there is
> > still a solution. The user can type ':map n :next<CR>'.
> >
> > Does anyone have any reservations about me removing this option?
> >
> > Does anyone support the idea of me removing this option?
> >
> > Thanks,
> > Bob Rossi
> >
> >   
> 
> Hello, Bob.
> 
> So, If you remember I don't support such removing at all. Because cgdb 
> with such shortcuts allows me not touch Fxx keys at all - same as I do 
> when I use vim.
> 
> But. If the next release allow full support of ":map" command in the 
> start config (and I'll be able to write 5-7 ":map" commands and receive 
> same functionality as it is now), let it be as you want :)

Yes, this is the intention, in fact, I'll write in the NEWS file the 
exact map commands that you can add to your .cgdbrc file to get the
behavior of shortcut mode.

Bob Rossi

Re: [Cgdb-users] deprecate shortcut mode

[Eugene V. L. <jac...@gm...>]

Bob Rossi wrote:
> Hi,
>
> I'm considering deprecating shortcut mode in the next release of cgdb.
>
> I get complaints on a monthly basis that when in shortcut mode, 'n'
> is 'next' in gdb, but it collides with the next search functionality.
>
> So, I'm thinking this is a flaw in the cgdb interface, all it does is
> confuse users. Currently, when in the source window,
>   F5 triggers the GDB 'run' command.
>   F6 triggers the GDB 'continue' command.
>   F7 triggers the GDB 'finish' command.
>   F8 triggers the GDB 'next' command.
>   F10 triggers the GDB 'step' command.
> These are all the shortcut options that you get while in shortcut mode.
> So, if I remove the shortcut mode option, you can still get all of the
> same functionality via the F keys.
>
> However, if a user is absolutely addicted to the shortcut mode, there is
> still a solution. The user can type ':map n :next<CR>'.
>
> Does anyone have any reservations about me removing this option?
>
> Does anyone support the idea of me removing this option?
>
> Thanks,
> Bob Rossi
>
>   

Hello, Bob.

So, If you remember I don't support such removing at all. Because cgdb 
with such shortcuts allows me not touch Fxx keys at all - same as I do 
when I use vim.

But. If the next release allow full support of ":map" command in the 
start config (and I'll be able to write 5-7 ":map" commands and receive 
same functionality as it is now), let it be as you want :)

[Cgdb-users] deprecate shortcut mode

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

Hi,

I'm considering deprecating shortcut mode in the next release of cgdb.

I get complaints on a monthly basis that when in shortcut mode, 'n'
is 'next' in gdb, but it collides with the next search functionality.

So, I'm thinking this is a flaw in the cgdb interface, all it does is
confuse users. Currently, when in the source window,
  F5 triggers the GDB 'run' command.
  F6 triggers the GDB 'continue' command.
  F7 triggers the GDB 'finish' command.
  F8 triggers the GDB 'next' command.
  F10 triggers the GDB 'step' command.
These are all the shortcut options that you get while in shortcut mode.
So, if I remove the shortcut mode option, you can still get all of the
same functionality via the F keys.

However, if a user is absolutely addicted to the shortcut mode, there is
still a solution. The user can type ':map n :next<CR>'.

Does anyone have any reservations about me removing this option?

Does anyone support the idea of me removing this option?

Thanks,
Bob Rossi

Re: [Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

[Eugene V. L. <jac...@gm...>]

Bob Rossi wrote:
> On Sat, Dec 01, 2007 at 03:27:32PM +0200, Eugene V. Lyubimkin wrote:
>> Bob Rossi wrote:
>>> On Sat, Dec 01, 2007 at 09:25:27AM +0200, Eugene V. Lyubimkin wrote:
>>>> Bob Rossi wrote:
>>>>> On Fri, Nov 30, 2007 at 10:03:52PM +0200, Eugene V. Lyubimkin wrote:
>>>>>> Have a good day.
>>>>>>
>>>>>> I noticed that key bindings for "send command 'next' to debugger" and
>>>>>> "next forward search in source window" are both - 'n'. I want to use
>>>>>> shortcuts, but therefore if I press 'n' gdb try to go the next line in
>>>>>> program, and I can't do a forward searching. Please fix it or provide a
>>>>>> workaround.
>>>>> Hi Eugene,
>>>>>
>>>>> Thanks for the report. Do you have any suggestions on what we could do
>>>>> to fix this problem? One suggestion I was given was to have the F1-F9
>>>>> keys handel the next/step/run functionality. Those are standardized on a
>>>>> lot of front ends.
>>>>>
>>>>> What do you think?
>>>>>
>>>>> Bob Rossi
>>>>>
>>>> Suggestion about F1-F9 seems good, anyway these keys aren't used now, 
>>>> are they?
>>>> But what do you think about changing 'forward search binding' key to 
>>>> 'y', for example? or 'w' - "forWard"?
>>> In the version you have, these commands should work,
>>>
>>>      F5 is now the same as 'r'.
>>>      F6 is now the same as 'c'.
>>>      F7 is now the same as 'f'.
>>>      F8 is now the same as 'n'.
>>>      F10 is now the same as 's'.
>>>
>>> Can you verify that that is true? I've added this to the documentation.
>> Yes, I can. I've verfied this bindings - all of the are working.
>> Hm... Probably, I'll start to use them as workaround of this situation.
>>> Also, I'm trying to figure out if I can use the imap command to have 'w'
>>> do what you want.
> 
> OK, here is the other solution that you can use with svn trunk. You can
> put this,
>   map w :set<Space>noshortcut<CR>n:set<Space>shortcut
> in your ~/.cgdb/cgdbrc
> 
> That will allow 'w' to act like 'n' when you are not in shortcut mode.
Why 'not in shortcut mode'? If I isn't in shortcut mode, the 'n' key 
works fine. Adding of new shortcut to 'forward search' is needed _in_ 
shortcut mode. Was it a mistype?
> Essentially allowing 'w' to do the next search. The only real downside
> is, it doesn't seem to highlight when you search. Let me know what you
> think about this.
I'll wait to new upstream release in Debian to get this functionality. 
If, as I understood, 'w' is an additional shortcut to 'forward search', 
it will be great for me.

Now building cgdb from trunk wants too much autotools' utilities and 
provides no .deb package, I have package-based system.
--

Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.

Re: [Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

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

On Sat, Dec 01, 2007 at 03:27:32PM +0200, Eugene V. Lyubimkin wrote:
> Bob Rossi wrote:
> > On Sat, Dec 01, 2007 at 09:25:27AM +0200, Eugene V. Lyubimkin wrote:
> >> Bob Rossi wrote:
> >>> On Fri, Nov 30, 2007 at 10:03:52PM +0200, Eugene V. Lyubimkin wrote:
> >>>> Have a good day.
> >>>>
> >>>> I noticed that key bindings for "send command 'next' to debugger" and
> >>>> "next forward search in source window" are both - 'n'. I want to use
> >>>> shortcuts, but therefore if I press 'n' gdb try to go the next line in
> >>>> program, and I can't do a forward searching. Please fix it or provide a
> >>>> workaround.
> >>> Hi Eugene,
> >>>
> >>> Thanks for the report. Do you have any suggestions on what we could do
> >>> to fix this problem? One suggestion I was given was to have the F1-F9
> >>> keys handel the next/step/run functionality. Those are standardized on a
> >>> lot of front ends.
> >>>
> >>> What do you think?
> >>>
> >>> Bob Rossi
> >>>
> >> Suggestion about F1-F9 seems good, anyway these keys aren't used now, 
> >> are they?
> >> But what do you think about changing 'forward search binding' key to 
> >> 'y', for example? or 'w' - "forWard"?
> > 
> > In the version you have, these commands should work,
> > 
> >      F5 is now the same as 'r'.
> >      F6 is now the same as 'c'.
> >      F7 is now the same as 'f'.
> >      F8 is now the same as 'n'.
> >      F10 is now the same as 's'.
> > 
> > Can you verify that that is true? I've added this to the documentation.
> Yes, I can. I've verfied this bindings - all of the are working.
> Hm... Probably, I'll start to use them as workaround of this situation.
> > Also, I'm trying to figure out if I can use the imap command to have 'w'
> > do what you want.

OK, here is the other solution that you can use with svn trunk. You can
put this,
  map w :set<Space>noshortcut<CR>n:set<Space>shortcut
in your ~/.cgdb/cgdbrc

That will allow 'w' to act like 'n' when you are not in shortcut mode.
Essentially allowing 'w' to do the next search. The only real downside
is, it doesn't seem to highlight when you search. Let me know what you
think about this.

Bob Rossi

Re: [Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

[Eugene V. L. <jac...@gm...>]

Bob Rossi wrote:
> On Sat, Dec 01, 2007 at 09:25:27AM +0200, Eugene V. Lyubimkin wrote:
>> Bob Rossi wrote:
>>> On Fri, Nov 30, 2007 at 10:03:52PM +0200, Eugene V. Lyubimkin wrote:
>>>> I noticed that key bindings for "send command 'next' to debugger" and
>>>> "next forward search in source window" are both - 'n'. I want to use
>>>> shortcuts, but therefore if I press 'n' gdb try to go the next line in
>>>> program, and I can't do a forward searching. Please fix it or provide a
>>>> workaround.
>>> Thanks for the report. Do you have any suggestions on what we could do
>>> to fix this problem? One suggestion I was given was to have the F1-F9
>>> keys handel the next/step/run functionality. Those are standardized on a
>>> lot of front ends.
>>>
>> Suggestion about F1-F9 seems good, anyway these keys aren't used now, 
>> are they?
>> But what do you think about changing 'forward search binding' key to 
>> 'y', for example? or 'w' - "forWard"?
> 
> OK, a little on how we got into this position. I added the shortcut keys
> I believe before we had the regex searching. 'n' seemed like the obvious
> key for 'next'. Then, I added the regex searching. A stated goal for
> CGDB is to have a similar feel, like vi/vim. So, the correct key for
> searching is 'n'. Now we had a collission. Along the way I had stopped
> using the shortcut keys. I was going to remove them from cgdb, but
> realized a lot of people had been using them.
> 
> So, I definately want to leave the next search as 'n'. However, I don't
> mind changing the shortcut keys, or adding another key  binding in
> shortcut mode that does the same thing.
> 
> With all of that said, the very next feature we plan to add to CGDB will
> be key mappings that allow you to bind a key to a particular piece of
> functionality. When that is done, you'll be able to map the
> functionality to whatever key you would like.
It will be great! :)
> 
> I'll add the F keys as a temporary solution, unless you can think of
> something immediately better.
Ok, this is also looks quite good.

-- 
Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.

Re: [Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

[Eugene V. L. <jac...@gm...>]

Bob Rossi wrote:
> On Sat, Dec 01, 2007 at 09:25:27AM +0200, Eugene V. Lyubimkin wrote:
>> Bob Rossi wrote:
>>> On Fri, Nov 30, 2007 at 10:03:52PM +0200, Eugene V. Lyubimkin wrote:
>>>> Have a good day.
>>>>
>>>> I noticed that key bindings for "send command 'next' to debugger" and
>>>> "next forward search in source window" are both - 'n'. I want to use
>>>> shortcuts, but therefore if I press 'n' gdb try to go the next line in
>>>> program, and I can't do a forward searching. Please fix it or provide a
>>>> workaround.
>>> Hi Eugene,
>>>
>>> Thanks for the report. Do you have any suggestions on what we could do
>>> to fix this problem? One suggestion I was given was to have the F1-F9
>>> keys handel the next/step/run functionality. Those are standardized on a
>>> lot of front ends.
>>>
>>> What do you think?
>>>
>>> Bob Rossi
>>>
>> Suggestion about F1-F9 seems good, anyway these keys aren't used now, 
>> are they?
>> But what do you think about changing 'forward search binding' key to 
>> 'y', for example? or 'w' - "forWard"?
> 
> In the version you have, these commands should work,
> 
>      F5 is now the same as 'r'.
>      F6 is now the same as 'c'.
>      F7 is now the same as 'f'.
>      F8 is now the same as 'n'.
>      F10 is now the same as 's'.
> 
> Can you verify that that is true? I've added this to the documentation.
Yes, I can. I've verfied this bindings - all of the are working.
Hm... Probably, I'll start to use them as workaround of this situation.
> Also, I'm trying to figure out if I can use the imap command to have 'w'
> do what you want.
> 
> Bob Rossi
-- 
Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.

Re: [Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

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

On Sat, Dec 01, 2007 at 09:25:27AM +0200, Eugene V. Lyubimkin wrote:
> Bob Rossi wrote:
> > On Fri, Nov 30, 2007 at 10:03:52PM +0200, Eugene V. Lyubimkin wrote:
> >> Have a good day.
> >>
> >> I noticed that key bindings for "send command 'next' to debugger" and
> >> "next forward search in source window" are both - 'n'. I want to use
> >> shortcuts, but therefore if I press 'n' gdb try to go the next line in
> >> program, and I can't do a forward searching. Please fix it or provide a
> >> workaround.
> > 
> > Hi Eugene,
> > 
> > Thanks for the report. Do you have any suggestions on what we could do
> > to fix this problem? One suggestion I was given was to have the F1-F9
> > keys handel the next/step/run functionality. Those are standardized on a
> > lot of front ends.
> > 
> > What do you think?
> > 
> > Bob Rossi
> > 
> Suggestion about F1-F9 seems good, anyway these keys aren't used now, 
> are they?
> But what do you think about changing 'forward search binding' key to 
> 'y', for example? or 'w' - "forWard"?

In the version you have, these commands should work,

     F5 is now the same as 'r'.
     F6 is now the same as 'c'.
     F7 is now the same as 'f'.
     F8 is now the same as 'n'.
     F10 is now the same as 's'.

Can you verify that that is true? I've added this to the documentation.
Also, I'm trying to figure out if I can use the imap command to have 'w'
do what you want.

Bob Rossi

Re: [Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

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

On Sat, Dec 01, 2007 at 09:25:27AM +0200, Eugene V. Lyubimkin wrote:
> Bob Rossi wrote:
> > On Fri, Nov 30, 2007 at 10:03:52PM +0200, Eugene V. Lyubimkin wrote:
> >> I noticed that key bindings for "send command 'next' to debugger" and
> >> "next forward search in source window" are both - 'n'. I want to use
> >> shortcuts, but therefore if I press 'n' gdb try to go the next line in
> >> program, and I can't do a forward searching. Please fix it or provide a
> >> workaround.
> > 
> > Thanks for the report. Do you have any suggestions on what we could do
> > to fix this problem? One suggestion I was given was to have the F1-F9
> > keys handel the next/step/run functionality. Those are standardized on a
> > lot of front ends.
> > 
> Suggestion about F1-F9 seems good, anyway these keys aren't used now, 
> are they?
> But what do you think about changing 'forward search binding' key to 
> 'y', for example? or 'w' - "forWard"?

OK, a little on how we got into this position. I added the shortcut keys
I believe before we had the regex searching. 'n' seemed like the obvious
key for 'next'. Then, I added the regex searching. A stated goal for
CGDB is to have a similar feel, like vi/vim. So, the correct key for
searching is 'n'. Now we had a collission. Along the way I had stopped
using the shortcut keys. I was going to remove them from cgdb, but
realized a lot of people had been using them.

So, I definately want to leave the next search as 'n'. However, I don't
mind changing the shortcut keys, or adding another key  binding in
shortcut mode that does the same thing.

With all of that said, the very next feature we plan to add to CGDB will
be key mappings that allow you to bind a key to a particular piece of
functionality. When that is done, you'll be able to map the
functionality to whatever key you would like.

I'll add the F keys as a temporary solution, unless you can think of
something immediately better.

Thanks,
Bob Rossi

Re: [Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

[Eugene V. L. <jac...@gm...>]

Bob Rossi wrote:
> On Fri, Nov 30, 2007 at 10:03:52PM +0200, Eugene V. Lyubimkin wrote:
>> Have a good day.
>>
>> I noticed that key bindings for "send command 'next' to debugger" and
>> "next forward search in source window" are both - 'n'. I want to use
>> shortcuts, but therefore if I press 'n' gdb try to go the next line in
>> program, and I can't do a forward searching. Please fix it or provide a
>> workaround.
> 
> Hi Eugene,
> 
> Thanks for the report. Do you have any suggestions on what we could do
> to fix this problem? One suggestion I was given was to have the F1-F9
> keys handel the next/step/run functionality. Those are standardized on a
> lot of front ends.
> 
> What do you think?
> 
> Bob Rossi
> 
Suggestion about F1-F9 seems good, anyway these keys aren't used now, 
are they?
But what do you think about changing 'forward search binding' key to 
'y', for example? or 'w' - "forWard"?

-- 
Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.

Re: [Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

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

On Fri, Nov 30, 2007 at 10:03:52PM +0200, Eugene V. Lyubimkin wrote:
> Have a good day.
> 
> I noticed that key bindings for "send command 'next' to debugger" and
> "next forward search in source window" are both - 'n'. I want to use
> shortcuts, but therefore if I press 'n' gdb try to go the next line in
> program, and I can't do a forward searching. Please fix it or provide a
> workaround.

Hi Eugene,

Thanks for the report. Do you have any suggestions on what we could do
to fix this problem? One suggestion I was given was to have the F1-F9
keys handel the next/step/run functionality. Those are standardized on a
lot of front ends.

What do you think?

Bob Rossi

[Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

[Eugene V. L. <jac...@gm...>]

Have a good day.

I noticed that key bindings for "send command 'next' to debugger" and
"next forward search in source window" are both - 'n'. I want to use
shortcuts, but therefore if I press 'n' gdb try to go the next line in
program, and I can't do a forward searching. Please fix it or provide a
workaround.
-- 
Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.

[Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

[Eugene V. L. <jac...@gm...>]

-------- Original Message --------
Subject: 'forward searching' and 'sending command next to debugger' have 
the same binding - 'n'
Date: Fri, 30 Nov 2007 21:53:17 +0200
From: Eugene V. Lyubimkin <jac...@gm...>
To: cgdb-users <cgd...@li...>

Have a good day.

I noticed that key bindings for "send command 'next' to debugger" and
"next forward search in source window" are both - 'n'. I want to use
shortcuts, but therefore if I press 'n' gdb try to go the next line in
program, and I can't do a forward searching. Please fix it or provide a
workaround.
-- 
Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.


-- 
Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.

Re: [Cgdb-users] compiling on OS X leopard

[Badi' Abdul-W. <ali...@gm...>]

On Nov 15, 2007, at 11:08 AM, Bob Rossi wrote:
> Hmmm, neosun had this compiling at some point. Have you seen the
> mac os X link here:
> http://cgdb.sourceforge.net/download.php
>
> It has a binary which you can use, unless you are relying on trunk/  
> for
> some reason.

I did see that. I'm trying to compile from source because I want  
tighter control over what I put on my computer, and (mainly) for the  
learning experience. I'm a bit new to using the *nixes and variants.


On Nov 15, 2007, at 11:08 AM, Bob Rossi wrote:
>> Does anyone have any idea as to what's going on? This seems to be
>> specific to the apple os, since I compiled and installed on a linux
>> box I have access to.
>
> Well, we would first need to know how to open a pty on mac os 10.5.  
> Once
> we figured that out, we can determine what's going wrong with  
> psuedo.c.
> Do you have a /dev/ptmx directory? How about /dev/ptc?

I do have a /dev/ptmx:
badi@eru [~/src/cvs-svn/cgdb]: file /dev/ptmx
/dev/ptmx: character special (15/2)

On Nov 15, 2007, at 11:58 AM, Bob Rossi wrote:
> Hi Badi,
>
> If I import the newest release of psuedo.c, will you test?

Sure.

btw, I wonder if this could have something to do with readline. I was  
having difficulty getting readling5.2 to build. I ended up changing  
the support/shobj-conf in the readline source directory to allow for  
darwin9 (leopard). The only changes I made were:
145:	darwin8*)									<----->	darwin9*)
and
156:	SHOBJ_LDFLAGS='-undefined dynamic_lookup' <----> 	SHOBJ_LDFLAGS='- 
undefined dynamic_lookup -dynamiclib'

Heres the link to my discovery on how to accomplish that:
http://forums.macosxhints.com/showthread.php?p=421408

Re: [Cgdb-users] compiling on OS X leopard

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

On Thu, Nov 15, 2007 at 08:50:35PM +0100, Horst Schirmeier wrote:
> On Thu, 15 Nov 2007, Bob Rossi wrote:
> > Well, we would first need to know how to open a pty on mac os 10.5. Once
> > we figured that out, we can determine what's going wrong with psuedo.c.
> > Do you have a /dev/ptmx directory? How about /dev/ptc?
> 
> I suggest looking at the location you borrowed that code from in the
> first place, maybe they already have a solution that works for Leopard
> (MacOS 10.5). 

Hi Badi,

If I import the newest release of psuedo.c, will you test?

Thanks,
Bob Rossi

Re: [Cgdb-users] compiling on OS X leopard

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

On Thu, Nov 15, 2007 at 08:50:35PM +0100, Horst Schirmeier wrote:
> On Thu, 15 Nov 2007, Bob Rossi wrote:
> > Well, we would first need to know how to open a pty on mac os 10.5. Once
> > we figured that out, we can determine what's going wrong with psuedo.c.
> > Do you have a /dev/ptmx directory? How about /dev/ptc?
> 
> I suggest looking at the location you borrowed that code from in the
> first place, maybe they already have a solution that works for Leopard
> (MacOS 10.5). As Cgdb builds fine on 10.4 here, it's very possible that
> this is a 10.5 only issue.
> 
> (MacOS 10.4.11)
> $ sudo port install cgdb
> Password:
> --->  Fetching cgdb
> --->  Attempting to fetch cgdb-0.6.4.tar.gz from
> http://downloads.sourceforge.net/cgdb
> --->  Verifying checksum(s) for cgdb
> --->  Extracting cgdb
> --->  Configuring cgdb
> --->  Building cgdb with target all
> --->  Staging cgdb into destroot
> --->  Installing cgdb 0.6.4_0
> --->  Activating cgdb 0.6.4_0
> --->  Cleaning cgdb

Great to see that it works on 10.4. Is it possible that you could send
us the translation unit for pseudo.c? That way, we could compare the
two examples. If you can set the CFLAGS, add -save-temps, then after the
build, psuedo.i should be left around by the compiler.

Thanks,
Bob Rossi