rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: netapp!byron@netcom.com (Byron Rakitzis)
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: memory leaks
Date: Thu, 13 Aug 1992 03:28:39 -0400	[thread overview]
Message-ID: <92Aug13.032857edt.2686@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 12 Aug 92 23:44:29 EDT." <9208130344.AA06713@netapp.netapp>


| Well, instead of being depressed about it you could send me some mail
| with a full bug report.

Sorry.  I needed to play empire for a while first. :-)

| I just looked at my rc-1.4 and I could not get it to leak on ^C. If you
| gave described the problem in full (are you using readline, maybe a
| prompt function doing something funny, etc.?) maybe somebody could do
| something about it.

I'm running vanilla 1.4 on a Sun sparc2 under 4.1.1, configured by
typing ``cp config.h-dist config.h''.   My prompt just prints status if
error.  Enclosed are some typescripts, one with an empty environment.
My supposition is that rc is longjmping out of an activation record
that has dynamically allocated some memory when it handles the sigint.

Script started on Thu Aug 13 03:05:27 EDT 1992
; exec ./rc-1.4-sun4
; ps v$pid
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26690 rf S     0:00  0  8      0   76  320    xx  0.0  2.2 rc
; ^C
; ps v$pid
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26690 rf S     0:00  0 15      0   76  324    xx  0.0  2.2 rc
; ^C
; ps v$pid
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26690 rf S     0:00  0 22      0   80  320    xx  0.0  2.2 rc
; ^C
; ps v$pid
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26690 rf S     0:00  0 30      0   80  324    xx  0.0  2.2 rc
; ^C
; ps v$pid
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26690 rf S     0:00  0 36      0   84  324    xx  0.0  2.2 rc
; ^C
; ^C
; ^C
; ^C
; ^C
; ^C
; ^C
; ^C
; ^C
; ^C
; ps v$pid
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26690 rf S     0:00  0 51      0  108  348    xx  0.0  2.4 rc
; Script done on Thu Aug 13 03:07:02 EDT 1992

Script started on Thu Aug 13 03:09:45 EDT 1992
; env - ./rc-1.4-sun4
; ps v$pid
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26717 p6 S     0:00  0 10      0   56  284    xx  0.0  1.9 rc
; ^C
; ^C
; ^C
; ^C
; ^C
; ^C
; ^C
; ^C
; ^C
; ^C
; ps v$pid
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26717 p6 S     0:00  0 22      0   80  308    xx  0.0  2.1 rc
; Script done on Thu Aug 13 03:10:23 EDT 1992

| (BTW, I hate to say this, but it peeves me a bit that you refer to the
| leak in the plural. 

Sorry about that.   I was speaking in generalities, "memory leaks"
being a single concept of which I discovered an instance.



  reply	other threads:[~1992-08-13  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-08-13  3:44 Byron Rakitzis
1992-08-13  7:28 ` Scott Schwartz [this message]
  -- strict thread matches above, loose matches on Subject: below --
1992-08-13 13:34 Chet Ramey
1992-08-13  2:08 Scott Schwartz
1992-08-13  4:32 ` John Mackin
1992-08-13  7:56   ` Scott Schwartz
1992-08-13 10:30     ` Mark-Jason Dominus

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=92Aug13.032857edt.2686@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).