qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Kovalenko <igor.v.kovalenko@gmail.com>
To: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Artyom Tarasenko <atar4qemu@googlemail.com>
Subject: Re: [Qemu-devel] gdb for sparc64?
Date: Sat, 4 Sep 2010 09:56:09 +0400	[thread overview]
Message-ID: <AANLkTinb=kkffPMaBwtF0EWKkpKnmdfJTuL+f4-JGz8S@mail.gmail.com> (raw)
In-Reply-To: <4C80BBA8.60405@siriusit.co.uk>

On Fri, Sep 3, 2010 at 1:11 PM, Mark Cave-Ayland
<mark.cave-ayland@siriusit.co.uk> wrote:
> Artyom Tarasenko wrote:
>
>> Does any gdb version work with current qemu-system-sparc64 ?
>>
>> I tried 7.1 and 6.8 with --target=sparc64-linux and --target=sparc64
>> And result seems to be pretty much the same:
>>
>> 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=x86_64-unknown-linux-gnu
>> --target=sparc64-linux".
>> (gdb) target remote :1234
>> Remote debugging using :1234
>> [New Thread 1]
>> Remote 'g' packet reply is too long:

Seems like set arch sparc:v9 helps:
http://lists.gnu.org/archive/html/qemu-devel/2009-01/msg00485.html

-- 
Kind regards,
Igor V. Kovalenko

      reply	other threads:[~2010-09-04  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 17:47 [Qemu-devel] gdb for sparc64? Artyom Tarasenko
2010-09-03  9:11 ` Mark Cave-Ayland
2010-09-04  5:56   ` Igor Kovalenko [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='AANLkTinb=kkffPMaBwtF0EWKkpKnmdfJTuL+f4-JGz8S@mail.gmail.com' \
    --to=igor.v.kovalenko@gmail.com \
    --cc=atar4qemu@googlemail.com \
    --cc=blauwirbel@gmail.com \
    --cc=mark.cave-ayland@siriusit.co.uk \
    --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).