Yours is a weird report.
>The application gives an error message in POSER
>"Dynamic heap chunk with header address..."
This message should never really appear. This is an "after the event" error
message. It is displayed only when Poser does a periodic check of the heap and
notices that something is wrong. However, Poser has enough checks in it that it
should always notice heap corruptions at the instant they occur. When it notices
at this time, it gives a different, more specific error message.
About the only thing I can think of that would corrupt the heap without warning
is a stack overflow. Poser used to check for stack overflows, but I had to turn
that code off because there were problems with it. I hope to be able to solve
those problems in the near future.
Or perhaps you've turned off some checkboxes in the Debug Options dialog that
would allow you to find the source of the corruption more easily.
>"Can't handle debug messages at this time."
Poser doesn't contain this error message. So either Poser is not displaying this
text, or it's displaying something else. If the latter, then I can't help you
unless I know what it's *really* saying.
-- Keith Rollin
-- Palm OS Emulator engineer
"Sudipta Ghose" <[EMAIL PROTECTED]> on 08/27/99 11:11:53 AM
Please respond to [EMAIL PROTECTED]
Sent by: "Sudipta Ghose" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (Keith Rollin/HQ/3Com)
Subject: Dynamic heap corruption
Hi all,
I have an app that has 3 code segments:
Segment 1: 71K
Segment 2: 64K
Segment 3: 62K
The application gives an error message in POSER
"Dynamic heap chunk with header address 0x0000BDAA got corrupted. The size
of the chunk (%chunk_size) was larger than the currently accepted maximum
(%chunk_max)".
In the actual device it simply gives fatal exception. I checked using the
debugger console, and it shows that heap 1 is corrupted - "Invalid Handle
field". I was guessing since segment 1 is more than 64K, it is causing the
error. However, reducing the size of segment 1 didn't help. Is there any
limit on a code segment size? I found out after several tries that the error
occurs while trying to allocate memory using MemHandleNew. However if I hit
the debug button during the error, POSER displays a message box saying
"Can't handle debug messages at this time." The only thing I can do at that
time is to hit Ctl-Alt-Delete, and terminate both POSER and CodeWarrior. Any
ideas what can cause such an error?
I am using:
Codewarrior 5.0 (with update and patch)
Windows 98 (with IE 5)
POSER 2.1D29
Palm III ROM/Palm 5000 ROM
Thanks for you help and patience.
-Sugho-
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
