Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Quality Quorum <qqi@world.std.com>
Cc: Christophe PLANAT <christophe.planat@st.com>, gdb@sources.redhat.com
Subject: Re: GDB and Kernel Object Display (KOD) info
Date: Wed, 10 Oct 2001 06:25:00 -0000	[thread overview]
Message-ID: <3BC44B0D.396AE94C@redhat.com> (raw)
In-Reply-To: <Pine.SGI.4.30.0110100828080.1834-100000@world.std.com>

Quality Quorum wrote:
> 
> On Wed, 10 Oct 2001, Christophe PLANAT wrote:
> 
> > Hello World !
> >
> > I search any information concerning the Kernel Objet Display remote
> > protocol used by GDB for the 'set os myos' and 'info myos' commands.
> >
> > In fact an example is given in the GDB release (kod-cisco.c) but the
> > details concerning the protocol description (request/reply) of qKoI,
> > qKaI, qKaL are not very clear.
> >
> > Does anybody knows where I can find info, others example, KOD protocol
> > definition ?
> 
> I suppose that unless you are working for cisco you have to invent
> your own protocol and command set in order to collect and display
> information relevant to your os.
> 

Yes, the idea is that the kod-*.c module understands what your OS kernel
sends to you.  In most cases you will pack your information in the 
special "K" packets of the remote protocol, so this will give you a 
few restrictions like having to send things in ASCII etc.
There are a few routines around to pack/unpack integers and other values
that you can "steal" from the sample stub implementations I think.

The version of your kod-*.c module should match your kernel version as
it is the one that understands the kernel structures that will be 
displayed and is responsible to format the output accordingly. 


Note that I need to change the way one registers a kod module.  It is
currently a static table and that obviously has to change.  I will add
a registration call if you really want to use it.

There is a KOD window in Insight.  It is a very simple one, but if you
follow some simple rules when formatting your output you can use that as
well.  


Fell free to ask me questions if you decide to use it.

Regards,
Fernando

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


      reply	other threads:[~2001-10-10  6:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10  2:39 Christophe PLANAT
2001-10-10  5:30 ` Quality Quorum
2001-10-10  6:25   ` Fernando Nasser [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BC44B0D.396AE94C@redhat.com \
    --to=fnasser@redhat.com \
    --cc=christophe.planat@st.com \
    --cc=gdb@sources.redhat.com \
    --cc=qqi@world.std.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox