From: Paul Durrant <paul.durrant@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: James Harper <james.harper@bendigoit.com.au>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: capturing windows crash dumps
Date: Wed, 19 Aug 2009 14:47:07 +0100 [thread overview]
Message-ID: <4A8C025B.7000608@citrix.com> (raw)
In-Reply-To: <20090819133510.GA26154@phenom.dumpdata.com>
Konrad Rzeszutek Wilk wrote:
>
> Not being familiar with Windows dumps, but only with Linux kdump (which is basically
> a mini-Linux distro running in 64MB - that includes the initrd.img and + RAM space)
> which can dump the entire memory on to whatever you want (NFS, disk, USB, etc).
>
> How does Windows natively/normally do its dump? Is it just dumping the entire memory space
> on the local disk? Or do you have to set special flags to do so from the driver?
>
Yes, it normally dumps it's memory to the device using a special
incarnation of the driver stack for that device.
Paul
--
===============================
Paul Durrant, Software Engineer
Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom
===============================
next prev parent reply other threads:[~2009-08-19 13:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 6:47 capturing windows crash dumps James Harper
2009-08-18 7:54 ` Keir Fraser
2009-08-18 10:42 ` James Harper
2009-08-18 12:10 ` Keir Fraser
2009-08-18 12:16 ` James Harper
2009-08-18 13:47 ` Stefano Stabellini
2009-08-18 23:53 ` James Harper
2009-08-19 10:28 ` James Harper
2009-08-19 10:38 ` Paul Durrant
2009-08-19 13:34 ` Stefano Stabellini
2009-08-19 13:35 ` Konrad Rzeszutek Wilk
2009-08-19 13:47 ` Paul Durrant [this message]
2009-08-20 9:56 ` James Harper
2009-08-20 10:22 ` Keir Fraser
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=4A8C025B.7000608@citrix.com \
--to=paul.durrant@citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=james.harper@bendigoit.com.au \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.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 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.