Re: Mixed debug/retail image
- From: charlez mutton <charlezmutton@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 20 Feb 2008 16:47:02 -0800
Perfect answer. Thnks.
"Dean Ramsier" wrote:
That's what the COMPILE_DEBUG flag is for..
--
Dean Ramsier - eMVP
BSQUARE Corporation
"charlez mutton" <charlezmutton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:98C3B20E-BCCE-4E2E-870A-F82F44F6DB26@xxxxxxxxxxxxxxxx
Yes you can still debug but the code is optimised so it does not debug
well.
What I want is to be able to turn off optimisations etc just for the one
driver that I am debugging.
Thanks for answering anyway.
"Luca Calligaris" wrote:
You can set 'Enable Kernel Debugger' options even for a release build:
this
configuration provides a more limited debugging respect to a debug build
but usually it's enough; if you set COMPILE_DEBUG=1 in the sources file
for
your driver that code will be compiled/linked as in a debug build.
By the way you do not need to call makeimg every time you rebuild your
driver: use 'Release Directory Modules' instead: the OS will load your
driver from
reldir instead that from ROM
--
Luca Calligaris
www.eurotech.it
"charlez mutton" <charlezmutton@xxxxxxxxxxxxxxxxxxxxxxxxx> ha scritto nel
messaggio news:21BD637D-D507-4C50-9921-0D98938C4B71@xxxxxxxxxxxxxxxx
Hi
A full debug image is just too slow and a full retail image is poor for
debugging.
I'd really like to be able to use a retail build ecxcept for the one
driver
I'm debugging.
A Google search suggests that there is a way to set "Always debug" on a
driver with some Platform Builder setting. Can someone please point
that
out
to me?
Alternatives like copying DLLs around + makeimg just seem a bit labor
intensive.
Thanks.
- References:
- Mixed debug/retail image
- From: charlez mutton
- Re: Mixed debug/retail image
- From: Luca Calligaris
- Re: Mixed debug/retail image
- From: charlez mutton
- Re: Mixed debug/retail image
- From: Dean Ramsier
- Mixed debug/retail image
- Prev by Date: Re: Bootstrap problem on WinCE 6.0 with MSVS2005 crashes...
- Next by Date: 16550 Over-run errors on 200 MHz Atmel AT91SAM9263 @ 115200 on Windows CE 6.0
- Previous by thread: Re: Mixed debug/retail image
- Next by thread: Re: Mixed debug/retail image
- Index(es):
Relevant Pages
|