🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.atari.st
Article #26063

Re: HDSCAN (two questions about 40-folder bug)

#26063
From: braner
Date: Sat, 04 Apr 1987 04:04
21 lines
1589 bytes
[]

Some things I don't understand about the "40-folders" bug (should be called
something else by now!):

Is calling the GEMDOS function Dfree() a possible danger?  (Does that cause
reading subdirectories, or does it simply read the FAT and count bits?)

Is repeated use of a program that uses dynamically-allocated RAM (e.g. micro-
EMACS) a danger?  I.e., when the program quits, are the blocks used for
keeping track of Malloc()ed RAM completely freed in the infamous, fixed-
size, system tables?  (Even if your compiler minimizes Malloc() calls by
Malloc-ing in big chunks and then malloc-ing out of it, it has to call
Malloc() at least once.)

- Moshe Braner

PS: could somebody send me "unshar" for the ST, or some other method for
easy transfer of many small files from a UNIX system to the ST?  Thanks.

PPS: still looking for a GEM metafile --> Postscript translator.
Technical Details
Message-ID: <605@batcomputer.tn.cornell.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!pyramid!batcomputer!braner
References: <104@stag.UUCP>

Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!pyramid!batcomputer!braner
From: braner@batcomputer.UUCP
Newsgroups: comp.sys.atari.st
Subject: Re: HDSCAN  (two questions about 40-folder bug)
Message-ID: <605@batcomputer.tn.cornell.edu>
Date: Fri, 3-Apr-87 23:04:46 EST
Article-I.D.: batcompu.605
Posted: Fri Apr  3 23:04:46 1987
Date-Received: Sun, 5-Apr-87 10:38:09 EST
References: <104@stag.UUCP>
Reply-To: braner@tcgould.tn.cornell.edu.UUCP (braner)
Organization: Theory Center, Cornell University, Ithaca NY
Lines: 21
Keywords: HDSCAN 40 FOLDER
Summary: Is Dfree() safe?  Malloc() and malloc behavior?