GNU bug report logs - #45117
28.0.50; process-send-string mysteriously exiting non-locally when called from timer

Previous Next

Full log

View this message in rfc822 format

From: João Távora <joaotavora <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>, 45117 <at> debbugs.gnu.org
Subject: bug#45117: 28.0.50; process-send-string mysteriously exiting non-locally when called from timer
Date: Fri, 11 Dec 2020 14:43:02 +0000

In Fri, Dec 11, 2020 at 2:40 PM Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> > From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> > Cc: joaotavora <at> gmail.com,  45117 <at> debbugs.gnu.org
> > Date: Fri, 11 Dec 2020 09:31:41 -0500
> >
> > > If currently process-send-string isn't protected against
> > > while-no-input, then perhaps we should add such a protection?
> >
> > Not just "perhaps" but "definitely".  This said, I believe it already is
> > "protected" so there's nothing we need to do (at least until we get
> > a bug report showing I'm wrong).
>
> I thought this bug report was showing just that, doesn't it?

Yes, the title is just that.  However, after digging down the
analysis I found that only a small fraction of the unexpected
quits I was getting actually happened in process-send-string.

So the title is a bit exaggerated, but it does happen.  I think
for larger strings, but not sure.

João

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.