zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: [BUG] malloc inside signal handler
Date: Thu, 26 Aug 2021 16:46:24 +0100 (BST)	[thread overview]
Message-ID: <1159264735.1176603.1629992784493@mail2.virginmedia.com> (raw)
In-Reply-To: <5509351db61721486dc9d27c7d816e8bea23b829.camel@ntlworld.com>

> On 18 August 2021 at 20:27 Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> 
> 
> On Tue, 2021-08-17 at 09:21 +0100, Peter Stephenson wrote:
> > Avoiding stdio for input of this sort doesn't actually look infeasible,
> > either --- mentions of bshin (buffered shell input from files) are
> > restricted to only a couple of files.  But it's kind of annoying as this
> > is exactly the job stdio is designed for.
> 
> As I noted, this isn't that difficult, and this should remove the
> problem --- all the memory management is now in places where we would
> expect it.
> 
> I don't know what the general feeling is about this, but as a piece of
> long-term robustness and with no immediately upcoming release I'd
> incline to getting this or something like it in for trying out.

I'm not hearing any objections to this.  I've checked it through again myself,
and can't see any problems or dubious areas, and I've been using it myself
for a week, so I'll check it in after waiting to see if there are any last
minute comments.

pws


  reply	other threads:[~2021-08-26 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 22:50 zsugabubus
2021-07-31  1:33 ` Bart Schaefer
2021-07-31 20:25   ` zsugabubus
2021-08-17  4:20     ` Bart Schaefer
2021-08-17  8:21       ` Peter Stephenson
2021-08-18 19:27         ` Peter Stephenson
2021-08-26 15:46           ` Peter Stephenson [this message]
2021-08-26 15:51             ` Bart Schaefer

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=1159264735.1176603.1629992784493@mail2.virginmedia.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).