Re: Disabling debug info through serial port

From: Remco (whybcuz_at_yahoo.com)
Date: 12/29/04 

Date: 29 Dec 2004 13:28:56 -0800

Hi Rob

Ok, I think that change allows you to use the debug port for both debug
and application. I think the routine that initializes the port and
sends the data is actually still alive. Kill them by putting a return
(without doing anything) on the OEMWriteDebugSerial function -- This is
the one that actually sends your debug data out.

Regards,
Remco

Relevant Pages

  • Re: Problem only in release version!
    ... the Debug version initializes most variables ... to zero. ... the contents of the memory addresses they happen to get assigned to). ...
    (microsoft.public.dotnet.languages.vc)
  • Re: [PATCH] USB and Driver Core patches for 2.6.10
    ... definitions for USB2 debug device, debug port ... This provides basic definitions to support "USB2 Debug Devices", ...
    (Linux-Kernel)
  • Re: How to test my serial driver
    ... Sometimes OAL will initialize aserialport to be a debug port for printing ... So the debug messages can be shown without anyserialportdriver. ...
    (microsoft.public.windowsce.embedded)
  • Re: Booting from usb problem
    ... Look at the debug port output. ... I built a debug kernel with KITL disabled. ... "Michel Verhagen (eMVP)" wrote: ...
    (microsoft.public.windowsce.embedded)
  • Re: Problem only in release version!
    ... >the Debug version initializes most variables to zero. ... In another bid to dispel this myth - a debug build doesn't do this. ... might have a higher probability of being zero in a debug build. ...
    (microsoft.public.dotnet.languages.vc)