From: Robert Barnes <robcb85@gmail.com>
To: gdb@sourceware.org
Subject: Switching architectures from a remote target
Date: Thu, 04 Feb 2010 19:38:00 -0000 [thread overview]
Message-ID: <23c0f921002041138k1d989b9cs8423911108499331@mail.gmail.com> (raw)
I am using GDB to interface with a remote target over serial. The
target architecture changes during execution (e.g. 32-bit to 64-bit).
When the architecture changes I need gdb to change its internal
representation of the remote architecture at the same time. The
primary problem is the remote 'g' command, it's return packet size is
determined by the initial call. When the architecture changes, the
size and number of registers may change, thus the size of the 'g'
packet changes. Yet gdb is still expecting the old size.
This problem is addressed in section 7 of "Multi-arching Insights and
GDB" by Andrew Cagney
(http://www.gnu.org/software/gdb/papers/multi-arch/real-multi-arch/).
As far as I can tell the recommendations haven't been implemented.
Are there any workarounds or solutions to the general problem of
handling changing architectures on a remote target?
Thanks!
-Rob
next reply other threads:[~2010-02-04 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 19:38 Robert Barnes [this message]
2010-02-05 6:50 ` Hui Zhu
2010-02-05 12:29 ` Jan Kiszka
2010-02-09 18:40 ` Robert Barnes
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=23c0f921002041138k1d989b9cs8423911108499331@mail.gmail.com \
--to=robcb85@gmail.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