This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 1119] windows applications terminates with 0xc0000005 un

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1119] windows applications terminates with 0xc0000005 under windows 64 bit / hvm
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 3 Dec 2007 12:36:15 -0800
Delivery-date: Mon, 03 Dec 2007 12:36:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1119-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

kamala.narasimhan@xxxxxxxxxx changed:

           What    |Removed                     |Added
                 CC|                            |kamala.narasimhan@xxxxxxxxxx

------- Comment #1 from kamala.narasimhan@xxxxxxxxxx  2007-12-03 12:36 -------
(In reply to comment #0)


If you can attach a crash dump of the crashing win32 process, I might be able
to analyze the crash and let you know what might be triggering the crash.  Here
are the steps to create a win32 crash dump (it assumes you either have control
over when the application is spawned or that you will have enough time to
attach to the process before the crash) -

1) Within the VM running W2k3, find out the process id of the crashing process
(using task manager).  If there is only a single instance of the application in
question, you may not need the process id, process name will do.
2) Use one of the below approach based on whether or not you can control
spawning the crashing app -
a) If you can manually spawn the crashing win32 application, spawn it under a
debugger using the below (within a command prompt) -

ntsd <application name>

Example - ntsd notepad.exe


b) If you can't directly spawn the crashing app, attach to the already spawned
instance (assuming you can do that before it crashes) - 

Spawn a command prompt and run the following command -
ntsd -p <crashing process id>
ntsd -pn <crashing process name>

3) This will spawn or attach the win32 application for debugging.  Press 'g' to
continue execution.
4) When the application crashes, ntsd debugger will automatically gain control.
 And when it does, from within ntsd run the following command -

.dump /ma <crash dump file name>

Example - .dump /ma xen-w2k3-userapp.dmp

If you can attach the crash dump to this issue, I might be able to investigate
further.  Also, if you can't control the target application using one of the
two approaches mentioned above, let me know.  We can explore alternate
approaches at that point.


Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 1119] windows applications terminates with 0xc0000005 under windows 64 bit / hvm, bugzilla-daemon <=