kdb wishlist

kdb wishlist

[Keith Owens]

This is part of my kdb wishlist, does anybody fancy writing the code to
add any of these features?  It would be a nice project for anybody
wanting to start on the kernel.  Replies to kdb@oss.sgi.com please.
Current patches at http://oss.sgi.com/projects/kdb/download/

* Change kdb invocation key from ^A to ^X^X^X within 3 seconds.  ^A is
  used by emacs, bash, minicom etc.

* Command history.  Handle up/down/left/right/delete keys.  Each
  kdba_io routine is responsible for recognising the arch specific
  keys, with a common history and editting routine.

* Clean up repeating commands.  Pressing enter at the kdb prompt
  repeats the previous command, no matter what the previous command
  was.  Some commands it makes no sense to repeat (bp in particular),
  for other commands you want to repeat the command but without the
  parameter (md in particular).

* Embed width and count options in md and mm commands.  Some hardware
  requires that accesses be a specific width, this can be achieved by
  setting BYTESPERWORD but it is awkward.  We want md1 to read one
  byte, md2, md4, md8 commands.  All can have a count field, e.g.
  md1c8 reads 8 bytes one at a time.  mm1, mm2, mm4, mm8 to set memory
  no count field.

Re: kdb wishlist

[Tigran Aivazian]

Keith,

What would be really great is to add the following item to your wishlist:

* make it possible (it is trivial but a pain to have to do it manually
every time I upgrade to your latest version!) for those extra "modules" to
be statically linked in. So that one doesn't have to keep these lines
in the rc.local
  
if [ -f /proc/sys/kernel/kdb ]
then
        insmod kdbm_pg > /dev/null 2>&1
        insmod kdbm_vm > /dev/null 2>&1
fi

and then discover that the modules are from the compilation corresponding
to a different tweak in page.h or highmem or whatever (let him who readeth
understand ;)

Long time ago I suggested removing the infrastructure for these "modules"
completely (justification being -- it is not useless _only_ in a very
exotic case of the need to teach kdb new features on a running kernel 
without permission to reboot) but you objected and that is fine, but at
least making it optionally possible would be _very nice_, please.

Regards,
Tigran

Re: kdb wishlist

[george anzinger]

Keith Owens wrote:
> 
> This is part of my kdb wishlist, does anybody fancy writing the code to
> add any of these features?  It would be a nice project for anybody
> wanting to start on the kernel.  Replies to kdb@oss.sgi.com please.
> Current patches at http://oss.sgi.com/projects/kdb/download/
> 
> * Change kdb invocation key from ^A to ^X^X^X within 3 seconds.  ^A is
>   used by emacs, bash, minicom etc.
> 
^X^X swaps point and mark in emacs.  One (well, I) often will do
^X^X^X^X to examine where mark is and then return to point.

George

~snip

Re: kdb wishlist

[slurn]

> 
> Keith Owens wrote:
> > 
> > This is part of my kdb wishlist, does anybody fancy writing the code to
> > add any of these features?  It would be a nice project for anybody
> > wanting to start on the kernel.  Replies to kdb@oss.sgi.com please.
> > Current patches at http://oss.sgi.com/projects/kdb/download/
> > 
> > * Change kdb invocation key from ^A to ^X^X^X within 3 seconds.  ^A is
> >   used by emacs, bash, minicom etc.
> > 
> ^X^X swaps point and mark in emacs.  One (well, I) often will do
> ^X^X^X^X to examine where mark is and then return to point.

How about using the break condition instead.  This is only for the
serial port, and most terminal emulators (e.g. kermit, minicom) provide
a means to generate a break condition on the serial port. 

scott

> 
> George
> 
> ~snip
> 

Re: kdb wishlist

[Juan Quintela]

>>>>> "slurn" == slurn  <slurn@verisign.com> writes:

>> 
>> Keith Owens wrote:
>> > 
>> > This is part of my kdb wishlist, does anybody fancy writing the code to
>> > add any of these features?  It would be a nice project for anybody
>> > wanting to start on the kernel.  Replies to kdb@oss.sgi.com please.
>> > Current patches at http://oss.sgi.com/projects/kdb/download/
>> > 
>> > * Change kdb invocation key from ^A to ^X^X^X within 3 seconds.  ^A is
>> >   used by emacs, bash, minicom etc.
>> > 
>> ^X^X swaps point and mark in emacs.  One (well, I) often will do
>> ^X^X^X^X to examine where mark is and then return to point.

slurn> How about using the break condition instead.  This is only for the
slurn> serial port, and most terminal emulators (e.g. kermit, minicom) provide
slurn> a means to generate a break condition on the serial port. 

kdb uses BREAK in the serial port (that minicom uses C-a for sending a
break is an anecdote :)  But the problem at hang is the console.  I
vote for the ^X^X^X as I a think that it is not a difficult shortcut.
(and yes, I also use emacs and ^X^X all the time, but I think that
this combination is not specially bad, and I suppose that the pet
aplication of other people will have problems with something like:
^A^A^A that I never use). 

Later, Juan.



-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

Re: kdb wishlist

[slurn]

> 
> >>>>> "slurn" == slurn  <slurn@verisign.com> writes:
> 
> >> 
> >> Keith Owens wrote:
> >> > 
> >> > This is part of my kdb wishlist, does anybody fancy writing the code to
> >> > add any of these features?  It would be a nice project for anybody
> >> > wanting to start on the kernel.  Replies to kdb@oss.sgi.com please.
> >> > Current patches at http://oss.sgi.com/projects/kdb/download/
> >> > 
> >> > * Change kdb invocation key from ^A to ^X^X^X within 3 seconds.  ^A is
> >> >   used by emacs, bash, minicom etc.
> >> > 
> >> ^X^X swaps point and mark in emacs.  One (well, I) often will do
> >> ^X^X^X^X to examine where mark is and then return to point.
> 
> slurn> How about using the break condition instead.  This is only for the
> slurn> serial port, and most terminal emulators (e.g. kermit, minicom) provide
> slurn> a means to generate a break condition on the serial port. 
> 
> kdb uses BREAK in the serial port (that minicom uses C-a for sending a
> break is an anecdote :)  But the problem at hang is the console.  I
> vote for the ^X^X^X as I a think that it is not a difficult shortcut.
> (and yes, I also use emacs and ^X^X all the time, but I think that
> this combination is not specially bad, and I suppose that the pet
> aplication of other people will have problems with something like:
> ^A^A^A that I never use). 
> 
> Later, Juan.

Unless something has changed, the console uses the 'pause' 
key and the serial port uses ^A (for x86, anyway).

I may be out of date, however.

scott

Re: kdb wishlist

[mirabilos]

> * Change kdb invocation key from ^A to ^X^X^X within 3 seconds.  ^A is
>   used by emacs, bash, minicom etc.

Why not Alt-SysRq-D (like Debug) or so?

> * Command history.  Handle up/down/left/right/delete keys.  Each
>   kdba_io routine is responsible for recognising the arch specific
>   keys, with a common history and editting routine.

yes!

> * Clean up repeating commands.  Pressing enter at the kdb prompt
>   repeats the previous command, no matter what the previous command
>   was.  Some commands it makes no sense to repeat (bp in particular),
>   for other commands you want to repeat the command but without the
>   parameter (md in particular).

Should be configurable. Sometimes I accidentally hit enter or do it
just to do something...

-mirabilos
-- 
EA F0 FF 00 F0 #$@%CARRIER LOST

Re: kdb wishlist

[Keith Owens]

On Tue, 8 May 2001 15:32:47 +0200, 
"Manfred Spraul" <manfred@colorfullife.com> wrote:
>One addtional wish list entry:
>
>'ss' and especially 'ssb' could print the new value of the overwritten
>register/memory address in each line, perhaps both the old and new
>value.

I don't need new wishlist entries, I need people to code the existing
requests!  How about code for this request :-)

Re: kdb wishlist

[Manfred Spraul]

One addtional wish list entry:

'ss' and especially 'ssb' could print the new value of the overwritten
register/memory address in each line, perhaps both the old and new
value.

--
    Manfred

Re: kdb wishlist

[r1vamsi]

Keith,

I have worked on the making md/mm take the width option using BYTESPERWORD.
I will be happy to work on this.

Regards.. Vamsi.

Vamsi Krishna S.
Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: +91 80 5262355 Extn: 3959
Internet: r1vamsi@in.ibm.com


Keith Owens <kaos@melbourne.sgi.com> on 05/08/2001 05:39:42 PM

Please respond to Keith Owens <kaos@melbourne.sgi.com>

To:   kdb@oss.sgi.com, linux-kernel@vger.kernel.org
cc:    (bcc: S Vamsikrishna/India/IBM)
Subject:  kdb wishlist




This is part of my kdb wishlist, does anybody fancy writing the code to
add any of these features?  It would be a nice project for anybody
wanting to start on the kernel.  Replies to kdb@oss.sgi.com please.
Current patches at http://oss.sgi.com/projects/kdb/download/

* Change kdb invocation key from ^A to ^X^X^X within 3 seconds.  ^A is
  used by emacs, bash, minicom etc.

* Command history.  Handle up/down/left/right/delete keys.  Each
  kdba_io routine is responsible for recognising the arch specific
  keys, with a common history and editting routine.

* Clean up repeating commands.  Pressing enter at the kdb prompt
  repeats the previous command, no matter what the previous command
  was.  Some commands it makes no sense to repeat (bp in particular),
  for other commands you want to repeat the command but without the
  parameter (md in particular).

* Embed width and count options in md and mm commands.  Some hardware
  requires that accesses be a specific width, this can be achieved by
  setting BYTESPERWORD but it is awkward.  We want md1 to read one
  byte, md2, md4, md8 commands.  All can have a count field, e.g.
  md1c8 reads 8 bytes one at a time.  mm1, mm2, mm4, mm8 to set memory
  no count field.