http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1119

kama...@citrix.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |kama...@citrix.com

------- Comment #1 from kama...@citrix.com 2007-12-03 12:36 ------- (In reply to comment #0)

Hi,

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

or

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> or 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.

Kamala