Re: [Q] TRacking down asserts by NdisTest

From: Mitesh Desai [MSFT] (miteshd_at_online.microsoft.com)
Date: 04/19/04 

Date: Mon, 19 Apr 2004 10:40:10 -0700

NDISTest 4.03.30 symbols are available in the packages at
http://www.microsoft.com/whdc/hwtest/device/default.mspx?area=network (for
4030030_32.exe, symbols are in i386\symbols\sys directory, for 4030030_64 in
ia64\symbols\sys).

NDISTest does not write anything in the registry before it triggers the
breakpoint.

>From a memory dump file it is not easy to figure out the reason for the
assert (because of compiler optimization asserts for different reasons get
combined into a single assert). If the breaking stack has your miniport on
it you can probably figure out what was happening. If its on receive code
paths (generally it is), see if you can find the packets which were just
indicated. The NDISTestHelp.chm document explains the NDISTest packet
format. You can verify if the packet length matches the expected length in
NDISTest protocol header if the data is valid. If its on the send code path,
its generally because packets are pending in the miniport.

Mitesh 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gramps" <gramps@old-fart.com> wrote in message
news:ePST1jiJEHA.1224@TK2MSFTNGP11.phx.gbl...
Howdy!
I trying to track down the cause of an assert within NdisTest 4.3.30.
Unfortunately, this assert happened on a machine that wasn't set up for the
debugger. So, the assert caused the system to crash
(KERNEL_MODE_EXCEPTION_NOT_HANDLED) so all I have is the memory dump. We're
trying to repro this with KD enabled on the machine, but...
Here's a couple of question:
Is the .pdb for ndistest.sys available anywhere?
Does ndistest.sys save anything meaningful in a register before it triggers
the int 3?
Assuming 2 is true, then is there documentation that would descibe the
register value for the reason for the assert?
Thanks!

Relevant Pages

  • Re: [Q] TRacking down asserts by NdisTest
    ... NDISTest does not write anything in the registry before it triggers the ... combined into a single assert). ... its generally because packets are pending in the miniport. ... Does ndistest.sys save anything meaningful in a register before it triggers ...
    (microsoft.public.development.device.drivers)
  • Re: [Q] TRacking down asserts by NdisTest
    ... decipher NDISTest protocol header. ... the assert was triggered at ... MiniportTransferData to get the rest of the packet. ...
    (microsoft.public.development.device.drivers)
  • Re: [Q] TRacking down asserts by NdisTest
    ... decipher NDISTest protocol header. ... the assert was triggered at ... MiniportTransferData to get the rest of the packet. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Help ! NDISTest - 2c_PerformanceProfile Test crashes intermittently
    ... The line "NdisTest: NdisPacketAllocateSend: NdtAllocatePacket failed on endpoint" seems to be the only useful clue. ... you must insure that original packets sent from higher level are eventually returned by calling NdisMSendComplete and that packets indicated to your ProtocolReceivePacket handler are eventually returned by calling NdisReturnPacket correctly. ... NdisTest: NdtDispatch: request COMPLETED by handler. ...
    (microsoft.public.development.device.drivers)
  • Re: [Q] TRacking down asserts by NdisTest
    ... the assert was triggered at ndistest!lNdtReceivePacketCommon+0x133. ... Does Ndistest handle receive lookahead indications where the lookahead buffer size may be smaller than the totla packet size? ... > Does ndistest.sys save anything meaningful in a register before it triggers ...
    (microsoft.public.development.device.drivers)
Loading