home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!network-analysis-ltd.co.uk!sw
- From: sw@network-analysis-ltd.co.uk (Sak Wathanasin)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: TCL: Bizzare Behavior Time
- Message-ID: <D2150050.nhutl1@nan.network-analysis-ltd.co.uk>
- Date: 12 Jan 93 22:50:30 GMT
- Reply-To: sw@network-analysis-ltd.co.uk
- Organization: Network Analysis Ltd
- Lines: 19
- X-Mailer: uAccess - Macintosh Release: 1.6v1
-
-
- In article <1993Jan11.170231.17969@fsl.noaa.gov> (comp.sys.mac.programmer), urban@yoda.fsl.noaa.gov (Art Urban) writes:
-
- > Swatch reports that my application's heap has gone BAD BAD BAD BAD
- > (Swatch's words, not mine). I followed the source code until this condition
- > occured, and it happens right after a call to new ( anObject ). My TRY,
-
- This just happened to me in the appl I am working on. This is a MacApp-based
- program not TCL, so I don't know how much of this applies to you. In my
- case, in my Initialize method, I was dereferencing a null pointer and trashing
- memory. You may find that your constructor or other initialization method
- is causing the bad heap. Good luck!
-
- Sak Wathanasin
- Network Analysis Limited
- 178 Wainbody Ave South, Coventry CV3 6BX, UK
-
- uucp: ...!uknet!nan!sw Phone: (+44) 203 419996
- AppleLink: NAN.LTD Internet: sw@network-analysis-ltd.co.uk
-