From: Jan Kiszka <jan.kiszka@web.de>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Max Filippov <jcmvbkbc@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Failed to use gdb with qemu 15.1 (with and without kvm support)
Date: Sun, 22 Jan 2012 22:15:59 +0100 [thread overview]
Message-ID: <4F1C7C8F.6030607@web.de> (raw)
In-Reply-To: <CAC9WiBj0bb0+Q-wyGN-YY9Chjtjicg_mzKNW8TRkQDM_OOj+gw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
On 2012-01-22 20:58, Francis Moreau wrote:
> On Sun, Jan 22, 2012 at 8:21 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> On 2012-01-22 20:16, Max Filippov wrote:
>>>> When stopping the guest with -S before it booted, gdb will interrupt it
>>>> while it is still in 16-bit real mode. Later on, when Linux runs, the
>>>> guest is in 64-bit protected mode. gdb is not prepared for such a
>>>> switch. All you can do:
>>>
>>> Try
>>>
>>> set arch i386:x86-64
>>>
>>> in the GDB prompt.
>>>
>>
>> Won't help if gdb already connected in 16/32-bit before.
>
> Why not ? is it a gdb bug ?
More than a bug, a deficit in the x86 target management of gdb. Requires
some work, but gdb people are at least aware of the issue.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-01-22 21:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 14:20 [Qemu-devel] Failed to use gdb with qemu 15.1 (with and without kvm support) Francis Moreau
2012-01-22 17:11 ` Michael Tokarev
2012-01-22 19:11 ` Francis Moreau
2012-01-22 19:36 ` Michael Tokarev
2012-01-22 18:49 ` Jan Kiszka
2012-01-22 19:16 ` Max Filippov
2012-01-22 19:21 ` Jan Kiszka
2012-01-22 19:58 ` Francis Moreau
2012-01-22 21:15 ` Jan Kiszka [this message]
2012-01-23 7:55 ` Francis Moreau
2012-01-22 19:29 ` Francis Moreau
2012-01-22 19:25 ` Francis Moreau
2012-01-22 19:28 ` Jan Kiszka
2012-01-22 19:57 ` Francis Moreau
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=4F1C7C8F.6030607@web.de \
--to=jan.kiszka@web.de \
--cc=francis.moro@gmail.com \
--cc=jcmvbkbc@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.