Prev: Video mirror driver in applications like VNC
Next: Device Simulation Framework
From: Alexander on 21 May 2008 02:01
Hello,

I have a problem with Windbg.
I have started it in debug mode and have waited for the debuggee to
connect. But I get the following outputs:

******************** OUTPUT BEGINNING ********************
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \\.\com1
Waiting to reconnect...
BD: Boot Debugger Initialized
Connected to Windows Boot Debugger 6001 x86 compatible target, ptr64
FALSE
Kernel Debugger connection established.
Symbol search path is: G:\Windows Vista\Symbols;G:\Projects\Pwe_common
\common\rssw\drsw\radar\pcirsc\windows\xp\i386
Executable search path is:
*** ERROR: Module load completed but symbols could not be loaded for
winload.exe
Windows Boot Debugger Kernel Version 6001 UP Free x86 compatible
Primary image base = 0x00584000 Loaded module list = 0x00684e58
System Uptime: not available
The call to LoadLibrary(bootext) failed, Win32 error 0n2
"Das System kann die angegebene Datei nicht finden."
Please check your debugger configuration and/or network access.
Shutdown occurred...unloading all symbol tables.
Waiting to reconnect...
******************** OUTPUT END ********************

The text in quotes means in English: "The system can not find the
given file"

If having an explicit break point in a DriverEntry routine the
debuggee will hang so debugger and debuggee really do not connect to
each other. But the null modem cable works and there are outputs if
the
debuggee boots in debug mode.

I think the critical point is "The call to LoadLibrary(bootext)
failed, Win32 error 0n2" and this is the reason for the shutdown of
the debugging engine.

Any idea concerning this error?

Thanks for any help,

Alexander Boegelsack
From: Tanya Radeva [MSFT] on 21 May 2008 17:28
Check your debug settings for the Target machine.

bcdedit /debug on
bcdedit /dbgsettings

Best regards,
Tanya

"Alexander" wrote:

> Hello,
>
> I have a problem with Windbg.
> I have started it in debug mode and have waited for the debuggee to
> connect. But I get the following outputs:
>
> ******************** OUTPUT BEGINNING ********************
> Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Opened \\.\com1
> Waiting to reconnect...
> BD: Boot Debugger Initialized
> Connected to Windows Boot Debugger 6001 x86 compatible target, ptr64
> FALSE
> Kernel Debugger connection established.
> Symbol search path is: G:\Windows Vista\Symbols;G:\Projects\Pwe_common
> \common\rssw\drsw\radar\pcirsc\windows\xp\i386
> Executable search path is:
> *** ERROR: Module load completed but symbols could not be loaded for
> winload.exe
> Windows Boot Debugger Kernel Version 6001 UP Free x86 compatible
> Primary image base = 0x00584000 Loaded module list = 0x00684e58
> System Uptime: not available
> The call to LoadLibrary(bootext) failed, Win32 error 0n2
> "Das System kann die angegebene Datei nicht finden."
> Please check your debugger configuration and/or network access.
> Shutdown occurred...unloading all symbol tables.
> Waiting to reconnect...
> ******************** OUTPUT END ********************
>
> The text in quotes means in English: "The system can not find the
> given file"
>
> If having an explicit break point in a DriverEntry routine the
> debuggee will hang so debugger and debuggee really do not connect to
> each other. But the null modem cable works and there are outputs if
> the
> debuggee boots in debug mode.
>
> I think the critical point is "The call to LoadLibrary(bootext)
> failed, Win32 error 0n2" and this is the reason for the shutdown of
> the debugging engine.
>
> Any idea concerning this error?
>
> Thanks for any help,
>
> Alexander Boegelsack
>
 | 
Pages: 1
Prev: Video mirror driver in applications like VNC
Next: Device Simulation Framework