From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: Testing the gnutls support
Date: Sat, 09 Oct 2010 15:56:04 +0200 [thread overview]
Message-ID: <m3y6a7eah7.fsf@quimbies.gnus.org> (raw)
In-Reply-To: 83mxqnmqqy.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> Debugger entered--Lisp error: (file-error "writing to process" "interrupted system call" #<process http<1>>)
>> process-send-string(#<process http<1>> "GET /market.php HTTP/1.0.\n.\n")
>
> That's strange. process-send-string calls emacs_write to write to the
> process, but emacs_write already handles EINTR, by retrying the write
> which failed. So why does this signal raise a Lisp error?
This is in emacs_gnutls_write, not emacs_write. But thanks for the
tip -- it was indeed faulty EINTR handling. I've now peeked at the
gnutls documentation and changed it to use the proper EINTR handling it
needs, and it seems to work in my test cases now.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-10-09 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 21:42 Testing the gnutls support Lars Magne Ingebrigtsen
2010-10-08 13:45 ` Ted Zlatanov
2010-10-09 13:18 ` Lars Magne Ingebrigtsen
2010-10-09 13:37 ` Eli Zaretskii
2010-10-09 13:56 ` Lars Magne Ingebrigtsen [this message]
2010-10-10 4:50 ` Ted Zlatanov
2010-10-10 15:26 ` Lars Magne Ingebrigtsen
2010-10-11 14:02 ` Ted Zlatanov
2010-10-11 16:25 ` Lars Magne Ingebrigtsen
2010-10-11 17:25 ` Ted Zlatanov
2010-10-14 21:37 ` Lars Magne Ingebrigtsen
2011-03-28 18:52 ` Ted Zlatanov
2011-03-28 19:08 ` Ted Zlatanov
2011-03-29 20:29 ` Lars Magne Ingebrigtsen
2011-04-01 14:35 ` Ted Zlatanov
2011-04-01 15:39 ` Lars Magne Ingebrigtsen
2011-04-01 20:11 ` Ted Zlatanov
2011-04-02 20:26 ` Lars Magne 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y6a7eah7.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.