RE: gdb remote stub for proprietary operating system?

Dominique Toupin (QA/EMC)
2007-01-23T22:46:01Z

Hi,

I have this info
http://sourceware.org/gdb/current/onlinedocs/gdb_18.html#SEC165, when
they say we can ignore the details I was hopping we could ignore the
communication protocol.
Do we have documentation other than sparc-stub.c?

If you have to choose between 3 months, 6 months, 1 year, 2 years, what
would be the guess for how long it would take 1 person to implement the
remote stub to support all the GDB/MI commands?

Thanks for your help,

/Dominique

-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org]
Sent: January 23, 2007 4:46 PM
To: Dominique Toupin (QA/EMC)
Cc: gdb@sourceware.org
Subject: Re: gdb remote stub for proprietary operating system?

On Tue, Jan 23, 2007 at 04:16:49PM -0500, Dominique Toupin (QA/EMC)
wrote:
> Hi,
>
> I would like to have info on how to implement a gdb remote stub for a
> proprietary operating system.
> How long does it typically take.

That depends on too many things for us to guess. For instance, how your
debug interfaces work within your OS, whether you are interested in
threading, and how much OS functionality you want to make available.
I recommend reading the remote protocol documentation from the GDB
manual, to get a feeling for how much you need. You won't need all the
packets documented there, though.

> My team will probably do a Linux GDB/MI implementation in DSF
> (http://www.eclipse.org/dsdp/dd/).

Great to hear someone is working on this - I am very interested in DSF.