From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sparc gdbserver: fix number of regs
Date: Tue, 13 Jan 2009 18:28:22 +0200 [thread overview]
Message-ID: <f43fc5580901130828s1e7c75efx24b2d99f2efa6af0@mail.gmail.com> (raw)
In-Reply-To: <6DAAE056-B357-4760-AF7D-3E2112240EDD@adacore.com>
On 1/13/09, Tristan Gingold <gingold@adacore.com> wrote:
> Hi,
>
> gdbstubs.c set the number of regs for sparc32 to 73 but gdb expects only
> 72. As a consequence, gdb
> doesn't accept 'g' packets (packets too long).
> This patch reduces the number of registers to 72. This is harmless as the
> 72nd register is not used and
> gdb accepts packets that contains less registers.
Excellent! Now my cross-gdb also works. The patch didn't apply but I
fixed it manually and then applied.
Maybe Sparc64 has the same problem?
next prev parent reply other threads:[~2009-01-13 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 15:14 [Qemu-devel] [PATCH] sparc gdbserver: fix number of regs Tristan Gingold
2009-01-13 16:28 ` Blue Swirl [this message]
2009-01-13 16:28 ` Blue Swirl
2009-01-13 16:37 ` Tristan Gingold
2009-01-13 18:20 ` Blue Swirl
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=f43fc5580901130828s1e7c75efx24b2d99f2efa6af0@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).