From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Arg fix
Date: Mon, 28 May 2001 10:46:53 -0400 [thread overview]
Message-ID: <20010528144656.0C3BC199DC@mail.cse.psu.edu> (raw)
Due to an editing mistake - mine - I omitted some cleanup code for the
newest wrap. It was in the original code, I just dropped it from the wrap.
How embarrassing.
Add the following to newproc(), creating /sys/src/9/port/proc.c:347,349
free(p->args);
p->args = nil;
p->nargs = 0;
It's not a huge problem, because sysexec frees the old args. The effect
of this mistake is to cause a process that forks without exec'ing to pick
up some stale, irrelevant arguments.
I'll update the files on the web later today.
-rob
next reply other threads:[~2001-05-28 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 14:46 rob pike [this message]
2001-05-28 17:11 rob pike
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=20010528144656.0C3BC199DC@mail.cse.psu.edu \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.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).