Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: bgat@billgatliff.com, Nicolas Moreau <nicolas@enttec.com>
Cc: gdb@sources.redhat.com
Subject: Re: RTOS awareness
Date: Wed, 14 Aug 2002 21:22:00 -0000	[thread overview]
Message-ID: <3D5B2C8B.9000308@ges.redhat.com> (raw)
In-Reply-To: <20020806203350.A1780@saturn.billgatliff.com>

> Nick:
> 
> 
> Pardon me from providing an incomplete answer, but you may also
> consider just having some "helper functions" with your stub or
> application that provide the needed functionality via printf()
> (redirected to gdb's console, for example).  You would call those
> functions from gdb's command line, rather than mucking with gdb source
> code.  No gdb mods required.
> 
> Just a thought.  I think eCos (another RTOS) uses this technique.

Also look at writing a few GDB scripts.  See ``printf''.  No reason to 
even write this in C.

Andrew


> b.g.
> 
> On Wed, Aug 07, 2002 at 11:20:19AM +1000, Nicolas Moreau wrote:
> 
>> Hi
>> 
>> I would like to write a UCOS II (embedded RTOS) awarness module 
>> for GDB to use on our embedded system. 
>> What I want to display is the data structure associated with each 
>> task, the display has to be in a user friendly format (no raw memory 
>> dump)
>> Where can I start ?
>> How can I extend the fucntionality of UCOS ?
>> What source files should I be looking at ?
>> 
>> Thanks
>> 
>> Nick
>> 
> 
> 
> -- Bill Gatliff bgat@billgatliff.com 



      parent reply	other threads:[~2002-08-15  4:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06 18:17 Nicolas Moreau
2002-08-06 18:33 ` William A. Gatliff
2002-08-06 18:57   ` Nicolas Moreau
2002-08-06 19:21     ` William A. Gatliff
2002-08-14 21:22   ` Andrew Cagney [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=3D5B2C8B.9000308@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=bgat@billgatliff.com \
    --cc=gdb@sources.redhat.com \
    --cc=nicolas@enttec.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