From: "Robert Norton" <rnorton@broadcom.com>
To: "jeremy.bennett@embecosm.com" <jeremy.bennett@embecosm.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: HOWTO for porting GDB published
Date: Wed, 03 Sep 2008 15:38:00 -0000 [thread overview]
Message-ID: <2DFD360E328B3941911E6D28B085D99010082C2745@SJEXCHCCR01.corp.ad.broadcom.com> (raw)
In-Reply-To: <1220352763.2870.178.camel@thomas>
> -----Original Message-----
> From: gdb-owner@sourceware.org
> [mailto:gdb-owner@sourceware.org] On Behalf Of Jeremy Bennett
> Sent: 02 September 2008 11:53
> To: gdb@sourceware.org
> Subject: HOWTO for porting GDB published
>
> I hope this is a useful contribution. I'd welcome feedback and any
> suggestions for how this first issue could be improved.
Wow this looks really great! I wish I'd had this when working on our port. It is difficult for me to be objective since perhaps I already know a little more about GDB than the target audience but I think this would have allowed me to get started much more easily.
Not having read the entire document thoroughly here are some things I really liked:
o It appears to give a clear and fairly high level explanation of the various concepts and terminology employed by GDB
o The example procedure flows (sequence diagrams) provide a good overview of gdb internals and where the arch functions fit in
o Provides a good checklist of things to do when porting an arch
o The OpenRISC example makes everything nice and concrete.
In short the whole thing seems to have hit a nice level of abstraction: high-level enough to provide information which can't be easily obtained by reading the source but not so high-level as to be totally abstract.
Thank you so much for this! Hopefully I will have time to give it a more thorough read sometime, at which point I may be able to give more detailed feedback.
Regards,
Robert Norton
next prev parent reply other threads:[~2008-09-03 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 10:53 Jeremy Bennett
2008-09-03 15:38 ` Robert Norton [this message]
2008-09-09 4:18 ` Joel Brobecker
2008-09-09 7:01 ` Jeremy Bennett
2008-09-13 23:09 ` Thiago Jung Bauermann
[not found] ` <1221346443.28258.50.camel@localhost.localdomain>
2008-09-16 9:39 ` Jeremy Bennett
2010-03-23 4:49 ` arm-none-linux-gnuabi - sim support? Reddy, MR Swami
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=2DFD360E328B3941911E6D28B085D99010082C2745@SJEXCHCCR01.corp.ad.broadcom.com \
--to=rnorton@broadcom.com \
--cc=gdb@sourceware.org \
--cc=jeremy.bennett@embecosm.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