Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: "Svein E. Seldal" <Svein.Seldal@solidas.com>, gdb@sources.redhat.com
Subject: Re: Porting advice or documentation request
Date: Thu, 29 May 2003 15:34:00 -0000	[thread overview]
Message-ID: <16086.10689.70706.173163@localhost.redhat.com> (raw)
In-Reply-To: <200305290949.h4T9nso00798@pc960.cambridge.arm.com>

Richard Earnshaw writes:
 > > Hi all,
 > > 
 > > I'm working on this new gdb port, and more than often I'm stuck. I have 
 > > been told that the d10v port is the most authorative template for how 
 > > new targets should be written. Unfortunately it is impossible to learn 
 > > anything about the d10v's hardware architecture on the net, so I find it 
 > > a bit difficult to template from.
 > 
 > I can sympathise.  I've tried on a couple of occasions to update the ARM 
 > target to use the new interfaces and I've repeatedly run into situations 
 > where the GDB's abstraction model is just not obvious from staring at the 
 > code.
 > 
 > Andrew, I think we really need a 10,000 ft view document on gdb's internal 
 > architecture to complement the list of macros that a target can define...
 > 
 > R.
 > 


I think checking out the new i386 frame branch could help here
too. Mark updated the i386 to use the new frame stuff, so that could
be used as example.

elena


  reply	other threads:[~2003-05-29 15:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 19:03 Porting advice Svein E. Seldal
2003-03-28 22:56 ` Andrew Cagney
2003-04-03  9:23   ` Svein E. Seldal
2003-04-05  1:54     ` Andrew Cagney
2003-05-28 22:55       ` Porting advice or documentation request Svein E. Seldal
2003-05-29  9:49         ` Richard Earnshaw
2003-05-29 15:34           ` Elena Zannoni [this message]
2003-05-29 18:54             ` Andrew Cagney
2003-03-31 18:17 ` Porting advice Corey Minyard
2003-03-31 21:16   ` Svein E. Seldal
2003-03-31 22:36     ` Corey Minyard

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=16086.10689.70706.173163@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Svein.Seldal@solidas.com \
    --cc=gdb@sources.redhat.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