rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Mark-Jason Dominus <mjd@saul.cis.upenn.edu>
To: Scott Schwartz <schwartz@groucho.cs.psu.edu>
Cc: The rc Mailing List <rc@hawkwind.utcs.toronto.edu>,
	mjd@saul.cis.upenn.edu
Subject: Re: memory leaks
Date: Thu, 13 Aug 1992 06:30:37 -0400	[thread overview]
Message-ID: <9208131030.AA17780@saul.cis.upenn.edu> (raw)
In-Reply-To: Your message of "Thu, 13 Aug 92 03:56:05 EDT." <92Aug13.035614edt.2686@groucho.cs.psu.edu>


> Hmmm.  Maybe there is something system specific involved?  I tested
> it on a sparc2 with gcc 2.2.2.

Ditto on our sparc2 and 690MP, with out-of-the-box config.h-dist and gcc v2.1.


  reply	other threads:[~1992-08-13 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
1992-08-13  3:44 Byron Rakitzis
1992-08-13  7:28 ` Scott Schwartz
1992-08-13 13:34 Chet Ramey

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=9208131030.AA17780@saul.cis.upenn.edu \
    --to=mjd@saul.cis.upenn.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=schwartz@groucho.cs.psu.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).