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

Re: Kernel Profiler - Required Compiler / Linker Switches? by Sue

Sue
Fri Jun 08 12:08:07 CDT 2007

This doc might help: http://msdn2.microsoft.com/en-us/library/aa936027.aspx
Though the info you need is in the "UNKNOWN Modules" section. I should get
that cleaned up a bit.

Are your modules in the "MODULES" section of ROM? The kernel profiler also
requires that.
If that's not possible, then the other thing you can do is use the
unsupported profiler+celog combination:
http://blogs.msdn.com/ce_base/archive/2006/01/23/516586.aspx

Sue
sloh@microsoft.com (remove "online" from reply-to address)
http://blogs.msdn.com/ce_base/
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________