TomPicard
Fri Aug 12 11:56:08 CDT 2005
thanks, yes you are right it is some beta or debug version
tom
"Doron Holan [MS]" wrote:
> also, are you sure you are running released (and not beta) bits? the file
> path does not look like a released binary to me.
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Scott Noone" <snoone@osr.com> wrote in message
> news:eH1aS7pnFHA.3656@TK2MSFTNGP09.phx.gbl...
> > Hi,
> >
> > Looks more like a hardcoded breakpoint than an ASSERT to me...
> >
> > Are you running a checked version of USBPORT? The free build on my XP dev
> > box shows this as the assembly for the dereference routine:
> >
> > lkd> u usbport!USBPORT_BusInterfaceDereference
> > USBPORT!USBPORT_BusInterfaceDereference:
> > f65bf396 c20400 ret 0x4
> >
> > So making that call doesn't actually do anything. I'd check out the
> > listing for the checked USBSTOR and see if it's just a DbgBreakPoint and a
> > return or if it looks like it's doing some other validation.
> >
> > -scott
> >
> > --
> > Scott Noone
> > Software Engineer
> > OSR Open Systems Resources, Inc.
> >
http://www.osronline.com
> >
> > "Tom Picard" <TomPicard@discussions.microsoft.com> wrote in message
> > news:4130112C-774F-404C-BDC1-893273E823EE@microsoft.com...
> >> trying to determine if my fast usb device is being plugged into a 1.1
> >> host
> >> on XP.
> >> So I try getting what is called the direct client access to USB Bus
> >> seems ok, get a pointer to the IsDeviceHighSpeed() function, it returns 1
> >> on
> >> ehci and 0 on uhci, that is good, no probelms.
> >> Not interested in the interface any more so I
> >> InterfaceDereference(BusInterfaceV1.BusContext) // identical parameter
> >> passed to IsDeviceHigh....
> >> and get an assert
> >> <TEST_TRAP> c:\sandbox\usb\rhcproto\ms24nov03\hcd\usbport\busif.c, line
> >> 116
> >> Break instruction exception - code 80000003 (first chance)
> >> nt!DbgBreakPoint:
> >> 8052a5cc cc int 3
> >> 0: kd>
> >> continues ok
> >> 1. Is there an easier way to determine what I need to know? or
> >> 2. any more info why am I getting an assert here? would checked build
> >> give
> >> me more details?
> >>
> >> Note: I don't think I am supposed to call InterfaceReference()
> >> but I tried that too and got an assert also
> >>
> >> Thanks
> >> tom
> >
> >
>
>
>