Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: "Simon Marchi" <simark@simark.ca>,
	"Maciej W. Rozycki" <macro@wdc.com>,
	"Jim Wilson" <jimw@sifive.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: Tue, 21 Jan 2020 13:47:00 -0000	[thread overview]
Message-ID: <mvmsgk9ey2u.fsf@suse.de> (raw)
In-Reply-To: <20200121130036.GI3865@embecosm.com> (Andrew Burgess's message of	"Tue, 21 Jan 2020 13:00:36 +0000")

On Jan 21 2020, Andrew Burgess wrote:

> If anyone knows of some instructions that will result in a RISC-V VM
> that works (defined as can configure/build GDB) do please let me know.

Not sure whether the QEMU linux-user emulation is good enough for
building GDB:

https://en.opensuse.org/openSUSE:RISC-V

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."


  reply	other threads:[~2020-01-21 13:30 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 [this message]
2020-01-22  0:11             ` Jim Wilson
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=mvmsgk9ey2u.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guoren@kernel.org \
    --cc=jiangshuai_li@c-sky.com \
    --cc=jimw@sifive.com \
    --cc=lifang_xia@c-sky.com \
    --cc=macro@wdc.com \
    --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