Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Jim Wilson <jimw@sifive.com>
Cc: "Simon Marchi" <simark@simark.ca>,
	"Maciej W. Rozycki" <macro@wdc.com>,
	jiangshuai_li@c-sky.com, "Guo Ren" <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 14:08:00 -0000	[thread overview]
Message-ID: <20200122133922.GJ3865@embecosm.com> (raw)
In-Reply-To: <CAFyWVaancBLpYdQhX=cvY76QFK-0DWR2pSFXBs5v5OCbKvMiaA@mail.gmail.com>

* Jim Wilson <jimw@sifive.com> [2020-01-21 22:15:30 -0800]:

> On Tue, Jan 21, 2020 at 4:11 PM Jim Wilson <jimw@sifive.com> wrote:
> > fix this.  It helps if you mention exactly which fedora image you are
> > using and exactly which qemu version you are using.
> 
> Using the 20191123 image and a top of tree qemu (4.2.50) binutils/gdb
> configure got stuck in gawk.  Looks like a bug with qemu.  I have a
> 3.1.92 qemu that got past configure and is now building which will
> probably take all night on my laptop.

Thank you!  That is exactly the issue I see too.

I'll try building 3.1.92 and see how that works for me - it would be
nice to have this working again.

Thanks,
Andrew


  reply	other threads:[~2020-01-22 13:39 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
2020-01-22  0:45           ` Jim Wilson
2020-01-22 10:19             ` Jim Wilson
2020-01-22 14:08               ` Andrew Burgess [this message]
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=20200122133922.GJ3865@embecosm.com \
    --to=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