Re: OAL logging library
- From: "K. S. Huang" <ksh_AT_bsquare_DOT_com>
- Date: Mon, 11 Sep 2006 18:41:28 +0800
While OALLog will still work in RETAIL mode, but as RETAILMSG they will
still be supressed when enabling SHIP build.
"Marco Contenti" <marco.contenti@xxxxxxxxxx>
???????:eD7uoLY1GHA.3644@xxxxxxxxxxxxxxxxxxxxxxx
Michel Verhagen (eMVP) ha scritto:
Define this in the file that contains your OEMInit function:
extern DBGPARAM dpCurSettings;
In OEMInit() do the following:
dpCurSettings.ulZoneMask = 0xMMMM
With 0xMMMM of course being the masks you want to enable. Be careful with
this though!
If you set ulZoneMask to 0xFFFF (all zones on), the kernel will HANG in
schedule.c! This is a bug, and a really nasty one (because who'd expect
turning on debug zones to help you debug a hanging kernel will in fact
hang the kernel... #$@%!@$%!)
This won't enable OALMSG's but the kernel debug output and only works with
a debug version of the kernel (which I don't recommend unless you are
having kernel-related problems).
As K.S.Huang wrote, OALMSG's are enabled by the global variable
g_oalLogMask. A good place could be on exit of the debug port
initialization function (usually in PLATFORM\??\SRC\COMMON\DBGSERIAL),
where this variable is initialized. Most important, it also works in
retail builds.
--
Marco Contenti
PROJECT s.a.s. (MSWEP)
www.projectsas.it
marco.contenti@<see domain above>
.
- References:
- OAL logging library
- From: IceBoot
- Re: OAL logging library
- From: Michel Verhagen (eMVP)
- Re: OAL logging library
- From: Marco Contenti
- OAL logging library
- Prev by Date: Re: Windows\SQLCE 2.0 directory
- Next by Date: Re: Is "Build and SysGen" needed?
- Previous by thread: Re: OAL logging library
- Next by thread: Re: OAL logging library
- Index(es):
Relevant Pages
|