Groups > Microsoft > WinDbg > Re: How to solve this condition after windbg connection?




How to solve this condition after windbg connection?

How to solve this condition after windbg connection?
Thu, 20 Mar 2008 00:10:42 -070
Dear Sir:

        I have some questions about setup windbg.

        I would download and install "WindowsXP-KB835935-SP2-
Symbols.exe" on my Host PC

        I try to connect both XP-SP2 PC to debug , but i found it
would run very slow or hang
        after show below message. I also can't control target pc and
don't type any commands,
        like "bp or bl". (show *BUSY*)

        How do i do to solve this condition?

//------------------------------------------------------------------------------
-----------------------------------------------------------------------//

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

Opened \\.\com1
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: C:\WINDOWS\Symbols;D:\Profilic\Src\Codec\Driver
\XP\src_ser2pl_2028\objchk_wxp_x86\i386;SRV*c:\WebSymbols*http://
msdl.microsoft.com/download/symbols
Executable search path is: D:\Profilic\Src\Codec\Driver\XP
\src_ser2pl_2028\objchk_wxp_x86\i386
Windows XP Kernel Version 2600 UP Free x86 compatible
<===spend more than 3-mins to show
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055b620
System Uptime: not available
Break instruction exception - code 80000003 (first chance)
<===spend more than 5-mins to show
*******************************************************************************
*
*
*   You are seeing this message because you pressed
either                    *
*       CTRL+C (if you run kd.exe)
or,                                        *
*       CTRL+BREAK (if you run
WinDBG),                                       *
*   on your debugger machine's
keyboard.                                      *
*
*
*                   THIS IS NOT A BUG OR A SYSTEM
CRASH                       *
*
*
* If you did not intend to break into the debugger, press the "g"
key,
then   *
* press the "Enter" key now.  This message might immediately
reappear.  If it *
* does, press "g" and "Enter"
again.                                          *
*
*
*******************************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export
symbols for ntoskrnl.exe -
nt!DbgBreakPointWithStatus+0x4:
804e4592 cc              int     3                   <===Prompt is
*BUSY*

Post Reply
Re: How to solve this condition after windbg connection?
Sat, 22 Mar 2008 14:22:52 -070
These are the typical symptoms of an attempt to resolve symbols
from the network.
If you are positive you have downloaded all of the symbols
to a local symbol cache, then, you can set `.sympath` to always look
at the local copy.
Other suggestion would be to clear-up stale breakpoints
and disable unqualified symbols resolution.

-- 

-- 
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"bluestar" <bluestar8783@gmail.com> wrote in message 
news:367946ff-0cf0-439a-8e64-b5143be3609c@s13g2000prd.googlegroups.com...
> Dear Sir:
>
>        I have some questions about setup windbg.
>
>        I would download and install "WindowsXP-KB835935-SP2-
> Symbols.exe" on my Host PC
>
>        I try to connect both XP-SP2 PC to debug , but i found it
> would run very slow or hang
>        after show below message. I also can't control target pc and
> don't type any commands,
>        like "bp or bl". (show *BUSY*)
>
>        How do i do to solve this condition?
>
>
//------------------------------------------------------------------------------
-----------------------------------------------------------------------//
>
> Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Opened \\.\com1
> Waiting to reconnect...
> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established.
> Symbol search path is: C:\WINDOWS\Symbols;D:\Profilic\Src\Codec\Driver
> \XP\src_ser2pl_2028\objchk_wxp_x86\i386;SRV*c:\WebSymbols*http://
> msdl.microsoft.com/download/symbols
> Executable search path is: D:\Profilic\Src\Codec\Driver\XP
> \src_ser2pl_2028\objchk_wxp_x86\i386
> Windows XP Kernel Version 2600 UP Free x86 compatible
> <===spend more than 3-mins to show
> Built by: 2600.xpsp_sp2_gdr.070227-2254
> Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055b620
> System Uptime: not available
> Break instruction exception - code 80000003 (first chance)
> <===spend more than 5-mins to show
>
*******************************************************************************
> *
> *
> *   You are seeing this message because you pressed
> either                    *
> *       CTRL+C (if you run kd.exe)
> or,                                        *
> *       CTRL+BREAK (if you run
> WinDBG),                                       *
> *   on your debugger machine's
> keyboard.                                      *
> *
> *
> *                   THIS IS NOT A BUG OR A SYSTEM
> CRASH                       *
> *
> *
> * If you did not intend to break into the debugger, press the "g"
key,
> then   *
> * press the "Enter" key now.  This message might immediately
> reappear.  If it *
> * does, press "g" and "Enter"
> again.                                          *
> *
> *
>
*******************************************************************************
> *** ERROR: Symbol file could not be found.  Defaulted to export
> symbols for ntoskrnl.exe -
> nt!DbgBreakPointWithStatus+0x4:
> 804e4592 cc              int     3                   <===Prompt is
> *BUSY*
>
> 

Post Reply
about | contact