I have an edit field, I create a new handle, copy the edit field data
to the newhandle, give the handle to a routine (from PG that adds or
replaces the resource, albeit in an external file), then write some
info to the datafork of the file, close the window. The datafork
portion seems to always get written, the resource portion, well, not
until you close the resource fork part of the file. Course by that
time, the app is sitting in Macsbug.


After a few tests of writing to the resource file :


MonacoPowerPC unmapped memory
exception at 001BE8DC BowelsOfTheMemoryMgr+06FBC

 Heap zones

  #1  Mod       11793K  00002800 to 00B86C3F  SysZone^

  #2  Mod           6K    0000C2A0 to 0000DE3F  ROM read-only zone

  #3  Mod          48K    001198C0 to 001258BF

  #4  Mod         384K    00842AF0 to 008A2AEF

  #5  Mod       51136K  00B86C40 to 03D76CDF  Process Manager zone

  #6  Mod        5817K    033F6B10 to 039A4F7F !  "FutureBASIC II" 
ApplZone^  TheZone^  TargetZone

  #7  Mod         895K    03C617A0 to 03D4164F  "Finder"

  #8  Mod          56K    03D51EE0 to 03D5FFEF  "Kensington Startup"

  #9  Mod          20K    03D66A60 to 03D6BD5F  "Eagle"

Checking all heaps

 The System heap at 00002800 is ok

 The ROM read-only heap at 0000C2A0 is ok

 The heap at 001198C0 is ok

 The heap at 00842AF0 is ok

 The Process Manager heap at 00B86C40 is ok

 The "FutureBASIC II" heap at 033F6B10 is bad

  This block's back pointer doesn't point to the previous block.

 Block header

  0387A8A0  6687 A270 AB20 0004  0000 0630 0000 74BC  fá¢p´ *****0**tº

 The "Finder" heap at 03C617A0 is ok

 The "Kensington Startup" heap at 03D51EE0 is ok

 The "Eagle" heap at 03D66A60 is ok

-----


What makes a heap zone go bad?


Mel Patrick - theWabbitGuy - mel@...

http://www.intergate.bc.ca/business/mel