From: broman@peanuts.nosc.mil (Vincent Broman)
To: rc@hawkwind.utcs.toronto.edu
Subject: Memory leaking
Date: Fri, 16 Apr 1993 15:00:22 -0400 [thread overview]
Message-ID: <9304161900.AA26560@trout.nosc.mil> (raw)
I run rc 1.4 on 386-Minix (and other machines) with the editline add-on.
I have a recurring problem that looks like a memory leak in rc.
After some time interacting with rc, I eventually type something
like "ls | more" and get one or two messages "Arg list too long",
which is perror output for the E2BIG error, happening in exec().
The problem is always fixable by doing "exec rc -l" and going on.
Since Minix fixes the memory allocated to a program at exec time
to a user-chosen, but modest, value, it appears that the program
is running out of memory. I checked my yacc and it doesn't seem
to malloc(). It is not impossible that the Minix exec() call itself is
buggy, but can anyone suggest any other avenues of investigation?
Anyone else see memory leaks not caused by yacc?
Vincent Broman, code 572 Bayside
Naval Command Control and Ocean Surveillance Center, RDT&E Div.
San Diego, CA 92152-6147, USA Email: broman@nosc.mil
next reply other threads:[~1993-04-16 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-04-16 19:00 Vincent Broman [this message]
1993-04-16 19:14 Byron Rakitzis
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=9304161900.AA26560@trout.nosc.mil \
--to=broman@peanuts.nosc.mil \
--cc=broman@trout.nosc.mil \
--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).