https://git.reactos.org/?p=reactos.git;a=commitdiff;h=23f6b36174fb7f735e724de9db6c46ebc8427a38
commit 23f6b36174fb7f735e724de9db6c46ebc8427a38 Author: Joachim Henze <[email protected]> AuthorDate: Tue Mar 10 22:48:02 2020 +0100 Commit: Joachim Henze <[email protected]> CommitDate: Tue Mar 10 22:48:02 2020 +0100 [USBHUB] Demote a DbgBreakPoint CORE-16394 The DbgBreakPoint() was reported to be continuable without obvious side-effects by Doug Lyons. Thank you for your tests Doug. To prevent what end-users may otherwise perceive as a freeze-regression caused by enabling the new driver in 0.4.13-dev-1048-g 6392c5a78c06ad8460deae47e90406fba0412bb5 --- drivers/usb/usbhub/ioctl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/usbhub/ioctl.c b/drivers/usb/usbhub/ioctl.c index 8cc42a88d67..a9da1f80f26 100644 --- a/drivers/usb/usbhub/ioctl.c +++ b/drivers/usb/usbhub/ioctl.c @@ -75,7 +75,7 @@ USBH_SelectConfigOrInterfaceComplete(IN PDEVICE_OBJECT DeviceObject, if (Urb->UrbHeader.Status == USBD_STATUS_NO_BANDWIDTH) { DPRINT1("USBH_SelectConfigOrInterfaceComplete: USBD_STATUS_NO_BANDWIDTH. FIXME\n"); - DbgBreakPoint(); + /*DbgBreakPoint();*/ /* disabled due to CORE-16384, seems to be continuable */ } }
