From: Ladi Prosek <lprosek@redhat.com>
To: Mihail Abakumov <mikhail.abakumov@ispras.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>,
sw@weilnetz.de, Pavel Dovgalyuk <dovgaluk@ispras.ru>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] WinDbg module
Date: Thu, 13 Apr 2017 09:02:45 +0200 [thread overview]
Message-ID: <CABdb734AjdU7kQOUzmmnhEdd0wmJWM4-2Fop=8jZ588uZX3M-w@mail.gmail.com> (raw)
In-Reply-To: <8a7bf9dbac4c6db5b7e8dd5c968cacae@ispras.ru>
Hi,
On Wed, Apr 12, 2017 at 4:05 PM, Mihail Abakumov
<mikhail.abakumov@ispras.ru> wrote:
> Hello.
>
> We made the debugger module WinDbg (like GDB) for QEMU. This is the
> replacement of the remote stub in Windows kernel. Used for remote Windows
> kernel debugging without debugging mode.
This is awesome!
> The latest build and instructions for the launch can be found here:
> https://github.com/ispras/qemu/releases/tag/v2.7.50-windbg
>
> Currently only one ways to create a remote debugging connection is
> supported: using COM port with named pipe.
The linked v2.7.50-windbg seems to be a Windows release. Does it also
work on Linux hosts with KVM?
Also,
#ifdef TARGET_X86_64 // Unimplemented yet
#error Unsupported Architecture
#endif
can you estimate the amount of work to support 64-bit?
Thanks!
Ladi
> Should I prepare patches for inclusion in the master branch? Or is it too
> specific module and it is not needed?
>
> --
> Thanks,
> Mihail Abakumov
>
next prev parent reply other threads:[~2017-04-13 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 14:05 [Qemu-devel] WinDbg module Mihail Abakumov
2017-04-12 15:49 ` Marc-André Lureau
2017-04-12 16:30 ` Roman Kagan
2017-04-12 17:55 ` Stefan Weil
2017-04-13 9:32 ` Mihail Abakumov
2017-04-12 18:47 ` Denis V. Lunev
2017-04-13 7:02 ` Ladi Prosek [this message]
2017-04-13 9:23 ` Mihail Abakumov
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='CABdb734AjdU7kQOUzmmnhEdd0wmJWM4-2Fop=8jZ588uZX3M-w@mail.gmail.com' \
--to=lprosek@redhat.com \
--cc=dovgaluk@ispras.ru \
--cc=mikhail.abakumov@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).