From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Using GDB to debug the sparc64 target
Date: Sun, 11 Jan 2009 17:12:27 +0200 [thread overview]
Message-ID: <f43fc5580901110712q743d713aw25c745edf91072c@mail.gmail.com> (raw)
In-Reply-To: <496A07B3.3090706@jermar.eu>
On 1/11/09, Jakub Jermar <jakub@jermar.eu> wrote:
> Hi,
>
> I'd like to help with debugging the sparc64 target (to get HelenOS
> run on it). I'd like to use gdb for that purpose, however, I get
> the following error when I try to connect to qemu from gdb:
>
> GNU gdb 6.8
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "--host=i686-pc-linux-gnu --target=sparc64-linux-gnu".
> (gdb) target remote localhost:1234
> Remote debugging using localhost:1234
> [New Thread 1]
> Remote 'g' packet reply is too long: 00000000000000000000000000000000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000001fff0000020000001fff00000240000000000000407000000000000000000000000000000000000000000000000
>
> Is this a known issue? Is there a workaround for this?
> The qemu version I am running is trunk, the host is
> an ordinary ia32 system.
The register size is still incorrect (32 bits) in the GDB you
produced. Also I can't make a working cross-gdb. The problem is on GDB
side: on Sparc64 OpenBSD, where everything is 64 bits, there is no
problem and the protocol matches what Qemu produces.
I'd be happy to be proven wrong, though. Currently my OpenBSD setup is
slightly broken, so this comes from memory.
next prev parent reply other threads:[~2009-01-11 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 14:52 [Qemu-devel] Using GDB to debug the sparc64 target Jakub Jermar
2009-01-11 15:12 ` Blue Swirl [this message]
2009-01-11 17:22 ` [Qemu-devel] " Jakub Jermar
2009-01-11 18:02 ` Blue Swirl
2009-01-11 20:34 ` Igor Kovalenko
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=f43fc5580901110712q743d713aw25c745edf91072c@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).