Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Anmol P. Paralkar" <b07584@freescale.com>
Cc: gdb@sourceware.org
Subject: Re: Question on 'set tdesc filename <path>'.
Date: Fri, 09 May 2008 17:26:00 -0000	[thread overview]
Message-ID: <20080509172623.GA11310@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0805091205160.22847@ld0159-tx32>

On Fri, May 09, 2008 at 12:18:21PM -0500, Anmol P. Paralkar wrote:
>  Oh, OK. So in these cases, the register ordering in the description
>  had better match-up what the remote-stub (implements and) sends - I
>  mean, since in the case where the remote side sends the
>  description, this is automatically ensured as GDB parses in the
>  XML.  I follow why the command is needed, thanks.

Right.

>> They are provided as reference, but also built-in to both GDB and
>> gdbserver for internal use.
>
>  So, in the case of PowerPC, the [pu]trace interface would only provide the standard 71
>  registers; what if we want to contribute back a description that defines more than those?
>  Is it OK for a description to have more than what the [pu]trace interface provides, since
>  you say that this gets built-in to GDB & gdbserver?

Specific descriptions are built in when GDB or gdbserver needs them.
Not every description is.  If you have new components to describe,
they won't go in the same descriptions that gdbserver is currently using.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2008-05-09 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 16:50 Anmol P. Paralkar
2008-05-09 16:59 ` Daniel Jacobowitz
2008-05-09 17:18   ` Anmol P. Paralkar
2008-05-09 17:26     ` Daniel Jacobowitz [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=20080509172623.GA11310@caradoc.them.org \
    --to=drow@false.org \
    --cc=b07584@freescale.com \
    --cc=gdb@sourceware.org \
    /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