From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: netapp!byron@netcom.com (Byron Rakitzis)
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Update on memory leaks
Date: Sat, 15 Aug 1992 20:54:18 -0400 [thread overview]
Message-ID: <92Aug15.205425edt.2613@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Sat, 15 Aug 92 01:45:03 EDT." <9208150545.AA17514@netapp.netapp>
It looks like it is Sun's yacc's fault. It mallocs space for the parse
stack at the top of yyparse, and frees it when YYACCEPT or YYABORT is
called. Unfortunately, longjmp defeats that strategy. Sun's ansi yacc
mallocs once and saves the pointer in global. Berkeley yacc statically
allocates things. Bison uses all sorts of techniques, but it seems to
work ok.
parent reply other threads:[~1992-08-16 0:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <9208150545.AA17514@netapp.netapp>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92Aug15.205425edt.2613@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--cc=netapp!byron@netcom.com \
--cc=rc@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).