I’ve been using network debugging during the development for a while, and
it works like charm.
Recently, I need to trouble shoot some WHCK failure with windbg. I thought
network debugging is a good option. But there are 2 problems with this
configuration:
a) the windows kernel network adapter will replace the original adapter,
and it will use a fresh new automatic generated IP address, which is very
likely different from the original static IP address, and it couldn’t be
reached from WHCK server.
b) the original network adapter will yellow bang. and the WHCK server will
deem it as a failure during some test.
How do you connect windbg during WHCK test?
If you use network debugging, what is the trick?
On DUT run DbgView as client, and try to capture the prints on Controller.
It worked for me.
Daniel
On Thu, Jul 4, 2013 at 5:21 PM, Danny wrote:
> I’ve been using network debugging during the development for a while, and > it works like charm. > > Recently, I need to trouble shoot some WHCK failure with windbg. I thought > network debugging is a good option. But there are 2 problems with this > configuration: > > a) the windows kernel network adapter will replace the original adapter, > and it will use a fresh new automatic generated IP address, which is very > likely different from the original static IP address, and it couldn’t be > reached from WHCK server. > > b) the original network adapter will yellow bang. and the WHCK server will > deem it as a failure during some test. > > How do you connect windbg during WHCK test? > If you use network debugging, what is the trick? > > > Thanks. > > – > Danny > — WINDBG is sponsored by OSR OSR is hiring!! Info at > http://www.osr.com/careers For our schedule of WDF, WDM, debugging and > other seminars visit: http://www.osr.com/seminars To unsubscribe, visit > the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer
On Thu, Jul 4, 2013 at 3:21 PM, Danny wrote: > I’ve been using network debugging during the development for a while, and it > works like charm. > > Recently, I need to trouble shoot some WHCK failure with windbg. I thought > network debugging is a good option. But there are 2 problems with this > configuration: > > a) the windows kernel network adapter will replace the original adapter, and > it will use a fresh new automatic generated IP address, which is very likely > different from the original static IP address, and it couldn’t be reached > from WHCK server. > > b) the original network adapter will yellow bang. and the WHCK server will > deem it as a failure during some test. > > How do you connect windbg during WHCK test? > If you use network debugging, what is the trick? > > > Thanks. > > – > Danny > — WINDBG is sponsored by OSR OSR is hiring!! Info at > http://www.osr.com/careers For our schedule of WDF, WDM, debugging and other > seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List > Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer
For the first problem, assign the same static address of the nw adapter to the kernel debug adapter. The OS tries to warn you that some other adapter has the same address but it is ok to proceed as both the adapter instances can’t be up and running at the same time.
Coming to the second issue, what WHCK tests are you trying to run? May be some more info will be helpful to give you suggestions.