From: "Anmol P. Paralkar" <b07584@freescale.com>
To: gdb@sourceware.org
Subject: Question on 'set tdesc filename <path>'.
Date: Fri, 09 May 2008 16:50:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0805091124340.22847@ld0159-tx32> (raw)
Hello,
Is there actually a scenario when the user would ask that the target description be
read from /<path> (locally, host-side) rather then relying on the default behaviour
to have GDB read the description from the target? What is the rationale for
'set tdesc filename <path>'? I would imagine that since ultimately, the target (stub)
defines the order in which it will send back the register values in response to a
g-packet, the target description should /always/ come from the target side - as is
the default behaviour. (So my understanding is that the XML descriptions provided
in the GDB sources are purely as reference for bare-metal application writers to use
in their remote-stub implementations).
But, perhaps I am missing something here; please could somebody tell me?
Thanks,
Anmol.
next reply other threads:[~2008-05-09 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 16:50 Anmol P. Paralkar [this message]
2008-05-09 16:59 ` Daniel Jacobowitz
2008-05-09 17:18 ` Anmol P. Paralkar
2008-05-09 17:26 ` Daniel Jacobowitz
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=Pine.LNX.4.64.0805091124340.22847@ld0159-tx32 \
--to=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