Re: query on pocket pc emulator and device
r_z_aret_at_pen_fact.com
Date: 03/05/05
- Next message: Tapani Saarinen: "Re: imgdecmp.dll (and SHLoadImage****)"
- Previous message: Robert Scott: "Re: How to rotate a bitmap (HBITMAP)"
- In reply to: Naveen koul: "query on pocket pc emulator and device"
- Next in thread: Naveen koul: "Re: query on pocket pc emulator and device"
- Reply: Naveen koul: "Re: query on pocket pc emulator and device"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 05 Mar 2005 14:49:03 -0500
On Sat, 5 Mar 2005 04:51:02 -0800, "Naveen koul"
<Naveenkoul@discussions.microsoft.com> wrote:
>Sir,
> i am developing my application on pocket pc device but i was using emulator
>2003.today when i loaded my release exe on to my pocket pc device and tried
>to execute it it showed me "out of memeory". but same aplication is running
>fine on pocket pc.
>the i checked the memory of my device it showed me 18.36 mb free. when i
>checked my pocket pc emulator memory it showed me 18.36 mb free.but my
>application is running quite fine on emulator but showing out of memory on
>device.
>but when that "out of memory" window appears when i click ook on it , my
>GUI comes afor while and vanishes up.
>
>i am not able to gather wht is the problem. how can i solve it.
>
>waiting for your reply.
>
>Regards
>
>Naveen koul
I suppose I'm one of the "evc boys" Daniel Moth mentioned, so I'll try
to help out.
I wouldn't take the actual error too literally. I suspect something
else has gone wrong. Also, I agree with Daniel Moth that differences
between emulator and real hardware are common. The fact that your
program runs on the emulator means it's at least OK. If you've really
run your program through Entrek, that is also a good sign.
I've never seen any dialog box like the one you describe, so that
doesn't provide much info for me.
My approach would be to use the debugger to narrow down the problem.
First, try running a debug version of your program on the actual
hardware, to make sure the symptom shows; debug and release builds
don't always behave the same. If the symptom does show with a debug
build, then you should put a breakpoint in WinMain, unless you are
using MFC. If you are using MFC, use whatever function is the
effective start (I don't use MFC, so I can't help here). If the
program gets to the first break without showing the symptom, you're in
good shape; keep adding break points until you get to the line of code
that triggers the symptom. If the symptom shows before WinMain
executes, then you are probably using C++ and the problem is in one of
your constructors. You can still narrow the search using break points,
but will need to think harder to figure out where to put the break
points.
My hunch is that once you find the line that triggers the symptom, you
will find out that the actual cause is somewhere else. Bad pointers
are almost always the prime suspects. Bad array indeces are a close
second.
I suspect you don't use ASSERTs. They are a bit of a pain to add, and
do make your source code less neat. But they are _very_ effective at
finding nasty problems such as bad pointers and array indeces. I
_strongly_ recommend using them. Check pointers and array indeces
right after you set them _and_ just before you use them. Check
function return values. Check _anything_ that might go wrong.
-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
Robert E. Zaret, eMVP
PenFact, Inc.
500 Harrison Ave., Suite 3R
Boston, MA 02118
www.penfact.com
- Next message: Tapani Saarinen: "Re: imgdecmp.dll (and SHLoadImage****)"
- Previous message: Robert Scott: "Re: How to rotate a bitmap (HBITMAP)"
- In reply to: Naveen koul: "query on pocket pc emulator and device"
- Next in thread: Naveen koul: "Re: query on pocket pc emulator and device"
- Reply: Naveen koul: "Re: query on pocket pc emulator and device"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
