Re: Debug and Release Builds???

Tech-Archive recommends: Speed Up your PC by fixing your registry

Without more information, I simply can't say what went wrong. I would have
to see the full call stack. In any case, you can probably just continue and
ignore the error.

--
-- Doug
///////////////////////////////////////////////////////////////////
// StdDisclaimer.h:
// This posting is provided "AS IS" with no warranties, and confers
// no rights.

"RH" <RH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E425DFE6-F3B3-4B5C-AD58-AFA2301C73CA@xxxxxxxxxxxxxxxx
Thanks for the reply Doug. I checked the call stack and it made reference
to
coredll and cgacutil. I am just having a hard time understanding what the
problem could be. I have made the simplest of OS images, following the
lab
by Paul Yao from the CE 6.0 Launch. So I don't understand what I can do
by
following the call stack. Any suggestions?

Thanks,

RH

"Doug Cook (MS)" wrote:

The debug builds of the OS will check for some extra error conditions and
stop when an error is found. The release builds will not notice the error
or
will try to recover. The idea is that you run the debug builds and find
all
of the errors, then create a release build with less error checking that
runs faster and fits in a smaller ROM.

The source line with the DEBUGCHK function explains what the error is:
Somebody called CloseHandle, but passed in an invalid handle value. You
can
find out who called CloseHandle by looking at the call stack in the
debugger.

--
//
// StdDisclaimer.h
// This posting is provided "AS IS" with no warranties, and confers no
rights.
//
"RH" <RH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:183CA5B9-6E38-4018-A913-53FC21342EF1@xxxxxxxxxxxxxxxx
Hi All,

I create an OS design using CE 6.0 in Debug configuration and run it on
the
device emulator. When I open another instance of VS2005 and try to
deploy
my
application to the device, it does not succeed. VS2005 gives me an
error
with the deployment and says
"C:\ymzki\private\winceos\COREOS\nk\kernel\nknormal\..\process.c at
line
248", which I think refers to
"c:\WINCE600\PRIVATE\WINCEOS\COREOS\NK\KERNEL\process.c". The PB
instance
of
VS2005 highlights the DEBUGCHK(0) (which is at line 248). Not sure
why?

The thing is, when I build and run the OS on the emulator in Release
mode,
there is no problem with attaching the device (emulator) or deploying
my
(C#)application.

Is there something that I am missing when I try to build a Debug build
of
my
OS image? Also, why can't my application be deployed on the OS Debug
image
running on the device emulator. The error I get when I try this is
using
the
Debug OS image is "An operation was attempted on something that is not
a
socket.". There is no problem with connecting to the device because I
can
ping the IP address obtained by s ipconfig /d (in the CE command shell)
from
my desktop and by clicking the connect to device button in VS2005.

I have ensured that I am running ConmanClient2 and CMAccept on the
device
emulator. I have tried this with different OS images and this seems to
always be the case.

Does anyone have any ideas of what could be happening? Or what I could
be
missing?

Thanks,

RH




.

Quantcast