Hi all,
I've got a driver I'm needing to profile that for various reasons
gets built via gmake on the command line in a tree completely outside
of the normal CE build process. This isn't an issue, but I'm trying
to profile the driver and think I'm missing something as all the
profiler hits inside the driver are getting registered as :
<UNACCOUNTED FOR>
Checking the documentation for the kernel profiler, normally in CE
land you include profiling info in a driver via :
1) set IMGPROFILER=1
2) set WINCEMAP=1
So I'm running a debug build and have checked that I'm generating map
files by specifying :
-map:drivername.map -mapinfo:lines
I also manually copied the drivers dll and test harness .exe as well as
associated files to the release directory just in case :
driver.dll
driver.map
driver.pdb
driver.rel
driver.dll
driver.dll
drivertest.ex2
drivertest.map
drivertest.pdb
However this didn't help so I'm leaning towards thinking that I've somehow
missed a compiler or linker flag thats needed. Any suggestions?
Cheers,
~Pev