From: Tim Goodwin <tjg@star.le.ac.uk>
To: jeremy@goop.org
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: minor nits picked up by valgrind
Date: Thu, 15 Aug 2002 11:28:30 -0500 [thread overview]
Message-ID: <20020815152830.14813.qmail@rocinante.star.le.ac.uk> (raw)
In-Reply-To: <1028096147.2444.57.camel@ixodes.goop.org> (jeremy@goop.org)
> Since valgrind[1] came out, I've been applying it to everything I can
> think of. rc was pretty clean, with one actual (but minor) problem and
> one non-problem.
OK, I'll buy both of these. Thanks!
And looking again at the signal code, I found a major booboo (of my
own making), which pulled in the horrid longjmp() code on systems
where it was needed.
With this, and some other problems I've fixed, there have been a few
changes since rc-1.7. A summary is appended, and please see my
hacking page for further details.
http://www.star.le.ac.uk/~tjg/rc/misc/notes
So, time for a new snapshot. Here it is:
http://www.star.le.ac.uk/~tjg/rc/snap/rc-1.7s20020815.tar.gz
Tim.
2002-07-25
Bug: fix globbing of broken symlinks.
2002-07-31
Bug: readline doesn't handle EIO either.
2002-08-15
Bug: variables that are sometimes exported (i.e. $prompt and
$version) need to be made exportable if they are inherited from the
environment.
Portability: don't call sigaction() for SIGKILL or SIGSTOP; don't
hand a garbage signal mask to sigaction() (thanks Jeremy
Fitzhardinge). Also, remove use of SA_INTERRUPT (SUSv3, BSD,
etc. have SA_RESTART with the inverted meaning).
prev parent reply other threads:[~2002-08-15 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 7:15 Jeremy Fitzhardinge
2002-08-15 16:28 ` Tim Goodwin [this message]
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=20020815152830.14813.qmail@rocinante.star.le.ac.uk \
--to=tjg@star.le.ac.uk \
--cc=jeremy@goop.org \
--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).