From: malte@TechFak.Uni-Bielefeld.DE
To: rc@hawkwind.utcs.toronto.edu
Subject: possible bug in rc 1.4
Date: Thu, 2 Dec 1993 05:56:32 -0500 [thread overview]
Message-ID: <9312021056.AA09324@pharao.techfak.uni-bielefeld.de> (raw)
Hello fellow rc users,
I'm afraid that I've found a bug in rc that I can easily reproduce on
Sparcs running Solaris 2.[2] and RS6000 running AIX 3.2.5, but not on
Sparcs running SunOS 4, DEC Alphas running OSF/1 1.3 and SGIs running
IRIX 4.0.5. On all machines, gcc 2.5.3 was used to compile the shell.
Consider running the following script:
#!/vol/local/bin/rc
fn sigint sighup { echo something >[1=2]; exit 1 }
while(){}
; script
[ run run run ]
^Csomething
;
Now I add sighup to the list of caught signals, rerun the script and
hit ^C again, the output is either "something" or
rc panic: unexpected node in doredirs!
or "something" followed by some blanks and newlines.
and is not reproducible. Adding another signal consistently causes an rc
panic. I believe that either r or r->r in doredirs gets corrupted but have
no idea why.
If I replace the invocation of echo with a call to another function echo'ing
the message with redirection, everything is fine.
Malte
reply other threads:[~1993-12-02 10:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9312021056.AA09324@pharao.techfak.uni-bielefeld.de \
--to=malte@techfak.uni-bielefeld.de \
--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).