🚀 go-pugleaf

well, it seems it should be simple enough to patch library calls such
as allocmem, freemem, openlibrary, closelibrary, etc. to track
resources intelligently, and patch remtask, i suppose, to make sure
everything was deallocated/closed.  either it could just close and
free everything left before removing the task, which has the clear
liability of breaking programs which *intentionally* leave the memory
allocated (to be freed by some other task) or a library open (to lock
it in memory) or whatever.  Alternatively, the tracker could alert the
user that resource _____ is still allocated, and allow the user to
decide whether to force release of none, some or all of the resources,
as he or she sees fit...  Of course, this could get annoying for the
user, so configuring it to take specific actions for specific programs
by default would be helpful, along with the ability to fully uninstall
the tracker, or to make it run silently, without harassing the user,
perhaps compiling a list of "naughty" programs.  The best use would be
fully interactive mode for testing and debugging programs, so that the
programmer could fix (or try to fix, at least) resource allocation
holes before using (and possibly releasing) the programs.

Does this sound feasible, or have I been hypnotized by this flickering
interlaced screen?

Deven
--
------- shadow@pawl.rpi.edu ------- Deven Thomas Corzine ---------------------
Cogito  shadow@acm.rpi.edu          2346 15th Street            Pi-Rho America
ergo    userfxb6@rpitsmts.bitnet    Troy, NY 12180-2306         (518) 272-5847
sum...     In the immortal words of Socrates:  "I drank what?"     ...I think.