From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3886 invoked by alias); 15 Aug 2002 04:22:57 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 3712 invoked from network); 15 Aug 2002 04:22:40 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 15 Aug 2002 04:22:40 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 7ED863CA9; Thu, 15 Aug 2002 00:22:35 -0400 (EDT) Message-ID: <3D5B2C8B.9000308@ges.redhat.com> Date: Wed, 14 Aug 2002 21:22:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020810 X-Accept-Language: en-us, en MIME-Version: 1.0 To: bgat@billgatliff.com, Nicolas Moreau Cc: gdb@sources.redhat.com Subject: Re: RTOS awareness References: <3D510273.8727.5B50901@localhost> <20020806203350.A1780@saturn.billgatliff.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00154.txt.bz2 > 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