From: Mihail Abakumov <mikhail.abakumov@ispras.ru>
To: Stefan Weil <sw@weilnetz.de>
Cc: Roman Kagan <rkagan@virtuozzo.com>,
qemu-devel@nongnu.org, Pavel Dovgalyuk <dovgaluk@ispras.ru>,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] WinDbg module
Date: Thu, 13 Apr 2017 12:32:12 +0300 [thread overview]
Message-ID: <b738b19aad6d0f4b7b55b0530b1b5382@ispras.ru> (raw)
In-Reply-To: <ec726281-486f-5448-4c3c-c28375c182cb@weilnetz.de>
Stefan Weil писал 2017-04-12 20:55:
> Am 12.04.2017 um 18:30 schrieb Roman Kagan:
>> On Wed, Apr 12, 2017 at 05:05:45PM +0300, Mihail Abakumov 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.
>>>
>>> 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.
>>>
>>> Should I prepare patches for inclusion in the master branch? Or is it
>>> too
>>> specific module and it is not needed?
>>
>> Please do!
>>
>> Every once in a while dealing with a Windows guest problem I wished I
>> had this. We at Virtuozzo looked into doing something like this but
>> never got around to.
>>
>> Thanks,
>> Roman.
>>
>
> Hello Mihail,
>
> from the previous answers you can see that there is a
> need for WinDbg support.
>
> If you want to prepare patches for the official QEMU,
> you need signed commits from all developers who contributed
> (Dmitry Koltunov and you?).
>
> Make also sure that no licensed code (for example extracts
> from MS header files) gets added.
>
> See http://wiki.qemu-project.org/Contribute/SubmitAPatch for
> more hints.
>
> As far as I saw, WinDbg support adds several thousand lines
> of code. Do you want to support that code after it has been
> included in QEMU?
>
> Cheers
> Stefan
Yes, of course. We can support it.
Thanks,
Mihail Abakumov
next prev parent reply other threads:[~2017-04-13 9:32 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 [this message]
2017-04-12 18:47 ` Denis V. Lunev
2017-04-13 7:02 ` Ladi Prosek
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=b738b19aad6d0f4b7b55b0530b1b5382@ispras.ru \
--to=mikhail.abakumov@ispras.ru \
--cc=dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--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).