GNU bug report logs - #44320
[PATH] [27.1] Make sure send-string-to-terminal send all contents

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: larsi <at> gnus.org, sunlin7 <at> yahoo.com, 44320 <at> debbugs.gnu.org, lin.sun <at> zoom.us
Subject: bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents
Date: Mon, 02 Nov 2020 19:10:06 +0200

> From: Andreas Schwab <schwab <at> linux-m68k.org>
> Cc: lin.sun <at> zoom.us,  larsi <at> gnus.org,  sunlin7 <at> yahoo.com,
>   44320 <at> debbugs.gnu.org
> Date: Mon, 02 Nov 2020 17:41:56 +0100
> 
> On Nov 02 2020, Eli Zaretskii wrote:
> 
> > So you are saying that the call to 'write' issued by 'fwrite' or
> > 'fflush' was interrupted by SIGIO, and that is why it didn't write all
> > of its data?
> 
> It wrote none of it.

I see in the trace a series of 'write' calls that write chunks of up
to 4K bytes:

  write(6, "!9?C...", 16384) = 4096
  write(6, "O??@...", 12288) = 4096
  write(6, "49!6...", 8192) = 4096
  write(6, "15!9...", 4096) = 2048
  write(6, "~~{F...", 2048) = 1792
  write(6, "D <at> b@...", 256) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)

So it looks like only the last call didn't write anything?  Or is my
interpretation wrong?

Previous Next

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