BugTrap and RapiDbg for Windows Mobile 6.0

I am trying to port a driver and several applications from a PocketPC 2003 (Windows CE 4.21) PDA to one running Windows Mobile 6 (CE 5.2).

Does anyone know if / how I can log the calls to OutputDebugString made by the driver without using the platform constructor or any custom OS image?

Porting is 99% complete, but I need to troubleshoot and debug something that is happening at the driver level.

So far, the combination of BugTrap (columbo) and RapiDbg has allowed me to debug the driver without having to build a platform. I was able to grab all of mine OutputDebugString

, pull them through activesync on my dev machine, and work from there.

Apparently bugtrap.exe doesn't work on WM6 (it crashes) and I can't find a new version.

Is there a way to trap (dump to file, send to host via USB, ... whatever) called OutputDebugString WITHOUT the need for a platform constructor or OS debug image?

I tried using the tracetool framework (see sourceforge), replacing the ODS call (fortunately all my debug statements use a macro) with my own Trace::Debug()->Send

, and normal DLLs and applications work as expected, the driver does not work.