Re: gawk memory leak

bobduff@world.std.com (Robert A Duff)
7 Apr 1997 15:02:29 -0400

          From comp.compilers
Related articles
[2 earlier articles]
Re: gawk memory leak albaugh@agames.com (1997-04-03)
Re: gawk memory leak stuart@cosc.canterbury.ac.nz (stuart(yeates)) (1997-04-06)
Re: gawk memory leak bobduff@world.std.com (1997-04-06)
Re: gawk memory leak max@gac.edu (Max Hailperin) (1997-04-06)
Re: gawk memory leak hbaker@netcom.com (1997-04-07)
Re: gawk memory leak cyber_surfer@wildcard.demon.co.uk (1997-04-07)
Re: gawk memory leak bobduff@world.std.com (1997-04-07)
Re: gawk memory leak clark@quarry.zk3.dec.com (1997-04-07)
Re: gawk memory leak arnold@mathcs.emory.edu (1997-04-08)
Re: gawk memory leak bobduff@world.std.com (1997-04-11)
Re: gawk memory leak marssaxman@sprynet.com.antispam (1997-04-11)
Re: gawk memory leak chase@naturalbridge.com (David Chase) (1997-04-11)
Re: gawk memory leak pfoxSPAMOFF@lehman.com (Paul David Fox) (1997-04-13)
| List of all articles for this month |
From: bobduff@world.std.com (Robert A Duff)
Newsgroups: comp.compilers
Date: 7 Apr 1997 15:02:29 -0400
Organization: The World Public Access UNIX, Brookline, MA
References: 97-03-165 97-04-020 97-04-022 97-04-040
Keywords: storage, GC, practice

Max Hailperin <max@gac.edu> wrote:
>In the garbage collected system, you need to reason locally:...
...
>In the manual-deallocation system, you need to reason globally: ...


Party (mostly?) true, but not entirely. Sometimes, pointers get stuck
into some global data structure (e.g. a hash table in a compiler, a
list-of-all-windows in a windowing system), and then the decision
becomes more global. Perhaps weak pointers are the solution here?
But GC alone doesn't completely localize the reasoning.


- Bob
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.