home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!sun-barr!decwrl!concert!sas!mozart.unx.sas.com!walker
- From: walker@twix.unx.sas.com (Doug Walker)
- Subject: Re: AllocMem corrupting memory
- Originator: walker@twix.unx.sas.com
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <BxGC01.8zJ@unx.sas.com>
- Date: Mon, 9 Nov 1992 13:55:13 GMT
- References: <1992Nov8.132440.14108@miavx1.acs.muohio.edu>
- Nntp-Posting-Host: twix.unx.sas.com
- Organization: SAS Institute Inc.
- Lines: 31
-
-
- In article <1992Nov8.132440.14108@miavx1.acs.muohio.edu>, bjbernstein@miavx1.acs.muohio.edu writes:
- |> I have been using AllocMem to create memory for 48 and 290 byte
- |> structures.. After creating a few of them (eventually, my program creates
- |> about 110 of them), I have noticed 'garbage' pixels appearing on the
- |> workbench screen, as if I wrote over some memory..
- |>
- |> Eventually, it crashes giving me a GURU of a corrupted freemem list..
- |>
- |> Should I be using AllocMem or is there some other routine that would be
- |> better for this?
-
- AllocMem is fine for this use; your program has a bug in it that
- causes problems. Get a copy of my "memlib" functions (they appeared
- on Fred Fish #240) and recompile your program and link with them.
- They are quite likely to be able to pinpoint your problem.
-
- If you have SAS/C 6.0, an improved version of memlib is shipped in
- the SC:EXTRAS/MEMLIB drawer.
-
- |> @@ Brian Bernstein (Drone) @@ "I'm a white dread, I'm a white @@
-
- --
- *****
- =*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
- *|. o.| || 1200/2400/9600 Dual
- | o |// For all you do, this bug's for you!
- ======
- usenet: walker@unx.sas.com bix: djwalker
- Any opinions expressed are mine, not those of SAS Institute, Inc.
-
-