When I use windbg to debug a vista machine. I always encounter a problem that the windbg will crazy printf some words as follows and it will never stop.If this happens,the vista machine will be very very slowly and the only thing I can do is rebooting it.
"
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Entered CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(136): Entered SxspValidateAssemblyIdentityAttributeName
d:\rtm\base\win32\fusion\sxs\ndpclassinfo.cpp(87): Entered SxspClrInteropContributorCallback
d:\rtm\base\win32\fusion\id\encdec.cpp(1448): Entered SxspValidateXMLName
d:\rtm\base\win32\fusion\sxs\ndpclassinfo.cpp(87): Exited SxspClrInteropContributorCallback
d:\rtm\base\win32\fusion\id\encdec.cpp(1448): Successfully exiting SxspValidateXMLName
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Successfully exiting CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(136): Successfully exiting SxspValidateAssemblyIdentityAttributeName
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Entered CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(160): Entered SxspValidateAssemblyIdentityAttributeValue
d:\rtm\base\win32\fusion\sxs\appsettings.cpp(225): Entered SxspApplicationSettingsContributorCallback
d:\rtm\base\win32\fusion\id\id.cpp(160): Successfully exiting SxspValidateAssemblyIdentityAttributeValue
d:\rtm\base\win32\fusion\sxs\appsettings.cpp(225): Exited SxspApplicationSettingsContributorCallback
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Successfully exiting CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(173): Successfully exiting SxsValidateAssemblyIdentityAttribute
d:\rtm\base\win32\fusion\id\id.cpp(535): Entered SxspFindAssemblyIdentityNamespace
d:\rtm\base\win32\fusion\id\id.cpp(73): Entered SxspValidateAssemblyIdentity
…
"
I even don’t have a path like “d:\rtm.…” in my system. My windbg is the lattest version of 6.10.0003.233 x86. And in vista machine I also add a “DEFAULT” key in HKLM\SYSTEM\CCS\Control\Session Manager\Debug Print Filter. The value is set to 0xf.
I can hardly debug vista system because of this problem. It’s happens occasionally and if it happens it will never stop until reboot. How does this happens? Can I set something in vista machine to disable it? Or can I prevent it in windbg setting?
Note that if you are using DbgPrint with a UNICODE_STRING and not limiting
the output, a UNICODE_STRING is not necessarily NUL-terminated. That would
be my first guess as to what is going wrong.
Show the code that is doing this, and it will be easier to determine what
might have happened and what the fix might be.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@dayang.com.cn
Sent: Monday, December 22, 2008 9:39 PM
To: Kernel Debugging Interest List
Subject: [windbg] How to disable the crazy printf in vista
When I use windbg to debug a vista machine. I always encounter a problem
that the windbg will crazy printf some words as follows and it will never
stop.If this happens,the vista machine will be very very slowly and the only
thing I can do is rebooting it.
"
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Entered
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(136): Entered
SxspValidateAssemblyIdentityAttributeName
d:\rtm\base\win32\fusion\sxs\ndpclassinfo.cpp(87): Entered
SxspClrInteropContributorCallback
d:\rtm\base\win32\fusion\id\encdec.cpp(1448): Entered SxspValidateXMLName
d:\rtm\base\win32\fusion\sxs\ndpclassinfo.cpp(87): Exited
SxspClrInteropContributorCallback
d:\rtm\base\win32\fusion\id\encdec.cpp(1448): Successfully exiting
SxspValidateXMLName
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Successfully exiting
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(136): Successfully exiting
SxspValidateAssemblyIdentityAttributeName
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Entered
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(160): Entered
SxspValidateAssemblyIdentityAttributeValue
d:\rtm\base\win32\fusion\sxs\appsettings.cpp(225): Entered
SxspApplicationSettingsContributorCallback
d:\rtm\base\win32\fusion\id\id.cpp(160): Successfully exiting
SxspValidateAssemblyIdentityAttributeValue
d:\rtm\base\win32\fusion\sxs\appsettings.cpp(225): Exited
SxspApplicationSettingsContributorCallback
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Successfully exiting
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(173): Successfully exiting
SxsValidateAssemblyIdentityAttribute
d:\rtm\base\win32\fusion\id\id.cpp(535): Entered
SxspFindAssemblyIdentityNamespace
d:\rtm\base\win32\fusion\id\id.cpp(73): Entered SxspValidateAssemblyIdentity
…
"
I even don’t have a path like “d:\rtm.…” in my system. My windbg is
the lattest version of 6.10.0003.233 x86. And in vista machine I also add a
“DEFAULT” key in HKLM\SYSTEM\CCS\Control\Session Manager\Debug Print Filter.
The value is set to 0xf.
I can hardly debug vista system because of this problem. It’s happens
occasionally and if it happens it will never stop until reboot. How does
this happens? Can I set something in vista machine to disable it? Or can I
prevent it in windbg setting?
You are currently subscribed to windbg as: xxxxx@flounder.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
–
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
I think this is system-supplied debug spew that goes under the default component; I seem to recall running into this before.
Side-by-side is not a good citizen.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Joseph M. Newcomer
Sent: Monday, December 22, 2008 9:59 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] How to disable the crazy printf in vista
Note that if you are using DbgPrint with a UNICODE_STRING and not limiting
the output, a UNICODE_STRING is not necessarily NUL-terminated. That would
be my first guess as to what is going wrong.
Show the code that is doing this, and it will be easier to determine what
might have happened and what the fix might be.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@dayang.com.cn
Sent: Monday, December 22, 2008 9:39 PM
To: Kernel Debugging Interest List
Subject: [windbg] How to disable the crazy printf in vista
When I use windbg to debug a vista machine. I always encounter a problem
that the windbg will crazy printf some words as follows and it will never
stop.If this happens,the vista machine will be very very slowly and the only
thing I can do is rebooting it.
"
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Entered
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(136): Entered
SxspValidateAssemblyIdentityAttributeName
d:\rtm\base\win32\fusion\sxs\ndpclassinfo.cpp(87): Entered
SxspClrInteropContributorCallback
d:\rtm\base\win32\fusion\id\encdec.cpp(1448): Entered SxspValidateXMLName
d:\rtm\base\win32\fusion\sxs\ndpclassinfo.cpp(87): Exited
SxspClrInteropContributorCallback
d:\rtm\base\win32\fusion\id\encdec.cpp(1448): Successfully exiting
SxspValidateXMLName
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Successfully exiting
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(136): Successfully exiting
SxspValidateAssemblyIdentityAttributeName
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Entered
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(160): Entered
SxspValidateAssemblyIdentityAttributeValue
d:\rtm\base\win32\fusion\sxs\appsettings.cpp(225): Entered
SxspApplicationSettingsContributorCallback
d:\rtm\base\win32\fusion\id\id.cpp(160): Successfully exiting
SxspValidateAssemblyIdentityAttributeValue
d:\rtm\base\win32\fusion\sxs\appsettings.cpp(225): Exited
SxspApplicationSettingsContributorCallback
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Successfully exiting
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(173): Successfully exiting
SxsValidateAssemblyIdentityAttribute
d:\rtm\base\win32\fusion\id\id.cpp(535): Entered
SxspFindAssemblyIdentityNamespace
d:\rtm\base\win32\fusion\id\id.cpp(73): Entered SxspValidateAssemblyIdentity
…
"
I even don’t have a path like “d:\rtm.…” in my system. My windbg is
the lattest version of 6.10.0003.233 x86. And in vista machine I also add a
“DEFAULT” key in HKLM\SYSTEM\CCS\Control\Session Manager\Debug Print Filter.
The value is set to 0xf.
I can hardly debug vista system because of this problem. It’s happens
occasionally and if it happens it will never stop until reboot. How does
this happens? Can I set something in vista machine to disable it? Or can I
prevent it in windbg setting?
You are currently subscribed to windbg as: xxxxx@flounder.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
–
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
You are currently subscribed to windbg as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Yes the crazy printf has nothing to do with my code. Sometimes it happens when I even has not load my driver. They look like system-supplied debug and I don’t know the meaning of them. It always happens when I do some little thing in vista, as open a window or open the device manager,etc.
I suspect that it will happen any time a .dll is loaded by LdrLoadDll, or a main process image is loaded. Aside from not using the default component, and mailing the SxS folks asking them to kindly get their act together, I’m not sure that there is much that you can really do here, unfortunately.
(Anyone happen to know a feedback alias for WinSxS, while we’re on this topic, btw?)
? S
-----Original Message-----
From: xxxxx@dayang.com.cn
Sent: Monday, December 22, 2008 21:30
To: Kernel Debugging Interest List
Subject: RE:[windbg] How to disable the crazy printf in vista
Yes the crazy printf has nothing to do with my code. Sometimes it happens when I even has not load my driver. They look like system-supplied debug and I don’t know the meaning of them. It always happens when I do some little thing in vista, as open a window or open the device manager,etc.
—
You are currently subscribed to windbg as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Given what Skywing reports, this probably won’t work, but you might want
to give it a try, just in case it’s not using the DEFAULT component.
ed nt!Kd_SXS_Mask 0
mm
Skywing wrote:
I think this is system-supplied debug spew that goes under the default component; I seem to recall running into this before.
Side-by-side is not a good citizen.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Joseph M. Newcomer
Sent: Monday, December 22, 2008 9:59 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] How to disable the crazy printf in vista
Note that if you are using DbgPrint with a UNICODE_STRING and not limiting
the output, a UNICODE_STRING is not necessarily NUL-terminated. That would
be my first guess as to what is going wrong.
Show the code that is doing this, and it will be easier to determine what
might have happened and what the fix might be.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@dayang.com.cn
Sent: Monday, December 22, 2008 9:39 PM
To: Kernel Debugging Interest List
Subject: [windbg] How to disable the crazy printf in vista
When I use windbg to debug a vista machine. I always encounter a problem
that the windbg will crazy printf some words as follows and it will never
stop.If this happens,the vista machine will be very very slowly and the only
thing I can do is rebooting it.
"
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Entered
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(136): Entered
SxspValidateAssemblyIdentityAttributeName
d:\rtm\base\win32\fusion\sxs\ndpclassinfo.cpp(87): Entered
SxspClrInteropContributorCallback
d:\rtm\base\win32\fusion\id\encdec.cpp(1448): Entered SxspValidateXMLName
d:\rtm\base\win32\fusion\sxs\ndpclassinfo.cpp(87): Exited
SxspClrInteropContributorCallback
d:\rtm\base\win32\fusion\id\encdec.cpp(1448): Successfully exiting
SxspValidateXMLName
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Successfully exiting
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(136): Successfully exiting
SxspValidateAssemblyIdentityAttributeName
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Entered
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(160): Entered
SxspValidateAssemblyIdentityAttributeValue
d:\rtm\base\win32\fusion\sxs\appsettings.cpp(225): Entered
SxspApplicationSettingsContributorCallback
d:\rtm\base\win32\fusion\id\id.cpp(160): Successfully exiting
SxspValidateAssemblyIdentityAttributeValue
d:\rtm\base\win32\fusion\sxs\appsettings.cpp(225): Exited
SxspApplicationSettingsContributorCallback
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Successfully exiting
CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(173): Successfully exiting
SxsValidateAssemblyIdentityAttribute
d:\rtm\base\win32\fusion\id\id.cpp(535): Entered
SxspFindAssemblyIdentityNamespace
d:\rtm\base\win32\fusion\id\id.cpp(73): Entered SxspValidateAssemblyIdentity
…
"
I even don’t have a path like “d:\rtm.…” in my system. My windbg is
the lattest version of 6.10.0003.233 x86. And in vista machine I also add a
“DEFAULT” key in HKLM\SYSTEM\CCS\Control\Session Manager\Debug Print Filter.
The value is set to 0xf.
I can hardly debug vista system because of this problem. It’s happens
occasionally and if it happens it will never stop until reboot. How does
this happens? Can I set something in vista machine to disable it? Or can I
prevent it in windbg setting?
You are currently subscribed to windbg as: xxxxx@flounder.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
–
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
You are currently subscribed to windbg as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
IIRC, the dbgctrl utility can be used to disable usermode spew?
If not: run Winternals DebugView with options to catch usermode
output and not pass it thru.
Does it help?
Regards,
–PA
xxxxx@dayang.com.cn wrote:
When I use windbg to debug a vista machine. I always encounter a problem that the windbg will crazy printf some words as follows and it will never stop.If this happens,the vista machine will be very very slowly and the only thing I can do is rebooting it.
"
d:\rtm\base\win32\fusion\sxs\actctxgenctxctb.cpp(447): Entered CActivationContextGenerationContextContributor::Fire_PCDATAParsed
d:\rtm\base\win32\fusion\id\id.cpp(136): Entered SxspValidateAssemblyIdentityAttributeName
…
> Given what Skywing reports, this probably won’t work, but you might want
to give it a try, just in case it’s not using the DEFAULT component.
ed nt!Kd_SXS_Mask 0
I think it’s actually nt!Kd_WIN2000_Mask. Such traces shouldn’t be shown
in kd by default, but some debugging tools might be changing the mask to
make these traces visible.
–
This posting is provided “AS IS” with no warranties, and confers no
rights.