title: BugTrap and RapiDbg on Windows Mobile 6.0
body: <p>I'm trying to port a driver and a few applications from a PDA running PocketPC 2003 (Windows CE 4.21) to one running Windows Mobile 6 (CE 5.2). </p>
  
  <p>Does anybody know if/how I can log the OutputDebugString calls made by the driver, short of using the Platform Builder or any custom OS image?</p>
  
  <p>Porting is 99% complete, but I need to troubleshoot and debug something that's happening at the driver level.</p>
  
  <p>Until now, the combination of BugTrap (columbo) and RapiDbg allowed me to debug the driver without the need of the Platform Builder. I was able to capture all my <code>OutputDebugString</code>, pull them via activesync on my dev machine and work from there.</p>
  
  <p>Apparently <strong>bugtrap.exe</strong> doesn't run on WM6 (it crashes) and I can't find any new version.</p>
  
  <p>Is there a way to trap (dump to file, send to host via USB, ... whatever) the OutputDebugString calls WITHOUT the need of the Platform Builder or of a debug image of the OS?</p>
  
  <p>I tried to use the tracetool framework (see sourceforge), replacing the ODS call (luckily all my debug statements use a macro) with its <code>Trace::Debug()-&gt;Send</code> and while regular DLLs and applications work as expected, the driver doesn't.</p>