Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: Andreas Schwab <schwab@suse.de>
Cc: "Andrew Burgess" <andrew.burgess@embecosm.com>,
	"Simon Marchi" <simark@simark.ca>,
	"Maciej W. Rozycki" <macro@wdc.com>,
	jiangshuai_li@c-sky.com, guoren@kernel.org,
	gdb-patches@sourceware.org, 夏立方 <lifang_xia@c-sky.com>,
	yunhai_shang <yunhai_shang@c-sky.com>
Subject: Re: [PATCH] riscv: add gdbserver support
Date: Wed, 22 Jan 2020 00:11:00 -0000	[thread overview]
Message-ID: <CAFyWVaY6QHOuCcSDKCDp3c0YvpJ9f62CaQ+09BgoqSX-c-C+mw@mail.gmail.com> (raw)
In-Reply-To: <mvmsgk9ey2u.fsf@suse.de>

On Tue, Jan 21, 2020 at 5:30 AM Andreas Schwab <schwab@suse.de> wrote:
> Not sure whether the QEMU linux-user emulation is good enough for
> building GDB:

No, I wouldn't recommend a user mode qemu for gdb work.  A system mode
qemu does work for building and running gdb.  I used this to develop
the risc-v linux native gdb port.  Though I suspect trying to run the
gdb testsuite on qemu would find some interesting risc-v qemu bugs.
It is possible to use a cross gdb with a program running on a system
or user mode qemu via target remote, though I don't test this very
often.

Jim


  reply	other threads:[~2020-01-21 23:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15  5:01 jiangshuai_li
2020-01-20 23:33 ` Jim Wilson
2020-01-21  0:30   ` Maciej W. Rozycki
2020-01-21  2:13     ` Simon Marchi
2020-01-21  2:17       ` Maciej W. Rozycki
2020-01-21 13:01       ` Andrew Burgess
2020-01-21 13:28         ` Andrew Burgess
2020-01-21 13:47           ` Andreas Schwab
2020-01-22  0:11             ` Jim Wilson [this message]
2020-01-22  0:45           ` Jim Wilson
2020-01-22 10:19             ` Jim Wilson
2020-01-22 14:08               ` Andrew Burgess
2020-01-21 23:56     ` Jim Wilson
2020-01-22  5:26   ` Guo Ren
2020-01-22  6:15     ` Jim Wilson

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=CAFyWVaY6QHOuCcSDKCDp3c0YvpJ9f62CaQ+09BgoqSX-c-C+mw@mail.gmail.com \
    --to=jimw@sifive.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guoren@kernel.org \
    --cc=jiangshuai_li@c-sky.com \
    --cc=lifang_xia@c-sky.com \
    --cc=macro@wdc.com \
    --cc=schwab@suse.de \
    --cc=simark@simark.ca \
    --cc=yunhai_shang@c-sky.com \
    /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