[coLinux-devel] Re: BSOD, DDK dependency

[Dan A. <da...@gm...>]

On Mon, Feb 02, 2004 at 12:14:17AM +0200, Dan Aloni wrote:

> I ask for anyone who experiences a BSOD with coLinux, please 
> extract useful information out from the tools Microsoft has 
> provided us:

I tried to use test these tools by deliberately causing an exception, 
and it appears they are very useful.

Using linux.pdb, which is also generated in the compilation, I am
able to produce a stacktrace such as:

nt!KiDispatchException+0x30e
nt!CommonDispatchException+0x4d
nt!KiUnexpectedInterruptTail+0x1f4
linux!co_os_file_block_read+0x3c
linux!co_monitor_file_block_service+0xc5
linux!co_monitor_block_request+0x41
linux!co_monitor_device_request+0x70
linux!co_monitor_iteration+0x107
linux!co_monitor_run+0x99
linux!co_monitor_ioctl+0x11e
linux!co_manager_ioctl+0xd5
linux!co_manager_dispatch+0xa4
nt!IopfCallDriver+0x35
nt!IopSynchronousServiceTail+0x60
nt!IopXxxControlFile+0x5e4
nt!NtDeviceIoControlFile+0x28
nt!KiSystemService+0xc4
ntdll!ZwDeviceIoControlFile+0xb
KERNEL32!DeviceIoControl+0x100
WARNING: Stack unwind information not available. Following frames may be 
wrong.
colinux_daemon+0x2f27
colinux_daemon+0x1b7e
colinux_daemon+0x1bb0
colinux_daemon+0x158d
colinux_daemon+0x1767
colinux_daemon+0x401a
colinux_daemon+0x7400
cygwin1!forkpty+0x3688
cygwin1!dll_crt0+0x1ad
colinux_daemon+0x7453
colinux_daemon+0x103c
KERNEL32!BaseProcessStart+0x3d

I'd like to see stack traces such as these, even before I send you a 
matched linux.pdb to the previously distributed linux.sys.

-- 
Dan Aloni
da...@gm...