From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, sunlin7@yahoo.com, 44320@debbugs.gnu.org,
LinSun <lin.sun@zoom.us>
Subject: bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents
Date: Mon, 02 Nov 2020 16:49:49 +0100 [thread overview]
Message-ID: <877dr321ya.fsf@igel.home> (raw)
In-Reply-To: <83eelbepw3.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 02 Nov 2020 17:31:56 +0200")
On Nov 02 2020, Eli Zaretskii wrote:
>> Date: Mon, 2 Nov 2020 11:11:22 +0800
>> From: LinSun <lin.sun@zoom.us>
>> Cc: "44320@debbugs.gnu.org" <44320@debbugs.gnu.org>
>>
>> Attach the log file ` testing-strace-2.log.gz` with a line more which may be a import hints.
>>
>> write(6, "…", 256) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
>
> Thanks.
>
> I don't think I know how to interpret this trace, or understand the
> significance of ERESTARTSYS.
It is translated to EINTR on signal handler return:
rt_sigreturn({mask=[]}) = -1 EINTR (Interrupted system call)
Outside of strace, ERESTARTSYS is never observed by user-space.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-11-02 15:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 23:01 bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents Lin Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-30 0:36 ` Lin Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-30 8:06 ` Eli Zaretskii
2020-10-30 12:38 ` Lars Ingebrigtsen
2020-10-30 13:25 ` Eli Zaretskii
2020-11-02 2:58 ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-02 3:11 ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-02 15:31 ` Eli Zaretskii
2020-11-02 15:49 ` Andreas Schwab [this message]
2020-11-02 16:14 ` Eli Zaretskii
2020-11-02 16:41 ` Andreas Schwab
2020-11-02 17:10 ` Eli Zaretskii
2020-11-02 17:36 ` Andreas Schwab
2020-11-02 17:59 ` Eli Zaretskii
2020-11-02 18:02 ` Andreas Schwab
2020-11-02 18:12 ` Eli Zaretskii
2020-11-02 18:22 ` Andreas Schwab
2020-11-02 18:35 ` Eli Zaretskii
2020-11-02 18:58 ` Andreas Schwab
2020-11-02 19:31 ` Eli Zaretskii
2020-11-02 20:26 ` Andreas Schwab
[not found] ` <4BD75783-F561-4DB8-A733-13A3D924C8C1@hxcore.ol>
2020-11-03 15:29 ` Eli Zaretskii
2020-11-05 0:14 ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-07 9:28 ` Eli Zaretskii
2020-11-09 2:27 ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-05 15:59 ` Eli Zaretskii
2020-11-05 16:07 ` Andreas Schwab
2020-11-02 15:22 ` Lars Ingebrigtsen
2020-11-02 16:07 ` Eli Zaretskii
2020-11-02 16:30 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dr321ya.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=44320@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=lin.sun@zoom.us \
--cc=sunlin7@yahoo.com \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).