From: "Marc Marí" <markmb@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Bug with GDB from commit ca3e40e
Date: Mon, 16 Nov 2015 12:16:34 +0100 [thread overview]
Message-ID: <20151116121634.732ffabb@markmb_rh> (raw)
In-Reply-To: <20151116084448-mutt-send-email-mst@redhat.com>
On Mon, 16 Nov 2015 08:45:09 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Mon, Nov 16, 2015 at 02:04:41AM +0100, Marc Marí wrote:
> > Hi
> >
> > I was trying to debug some stuff in the bootloader and the
> > optionrom, and I found a bug with QEMU and GDB. In commit ca3e40e
> > (a pull request from Michael), I get this:
> >
> > x86_64-softmmu/qemu-system-x86_64 --enable-kvm \
> > -kernel /boot/vmlinuz-4.1.7-200.fc22.x86_64 -s -S
> > qemu-system-x86_64: -s: address resolution failed for :: Name or
> > service not known
> >
> > In the previous commit (3c23402) I don't get the error:
> > x86_64-softmmu/qemu-system-x86_64 --enable-kvm \
> > -kernel /boot/vmlinuz-4.1.7-200.fc22.x86_64 -s -S
> > (Opens QEMU and blocks, as expected, and I can connect GDB)
> >
> > I cannot see the problem (maybe because it's a bit late). I'll look
> > at it again tomorrow, but any help is appreciated.
> >
> > My system is a Fedora 22, Linux 4.2.5-201, x86_64, and GDB version
> > 7.9.1-20.
> >
> > Thanks
> > Marc
>
> This command line seems to work for me.
>
Old QEMU version. Issue solved in commit 2ea1793.
It seems it has something to do with the port in InetSocketAddress in
qapi-schema.json.
I should not trace "bugs" until so late.
Thanks
Marc
prev parent reply other threads:[~2015-11-16 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 1:04 [Qemu-devel] Bug with GDB from commit ca3e40e Marc Marí
2015-11-16 6:45 ` Michael S. Tsirkin
2015-11-16 11:16 ` Marc Marí [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=20151116121634.732ffabb@markmb_rh \
--to=markmb@redhat.com \
--cc=mst@redhat.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).