From: Ken Brown <kbrown@cornell.edu>
To: 23540@debbugs.gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#23540: 25.1.50; make-ipv4-tcp-server-with-unspecified-port fails
Date: Sun, 15 May 2016 08:16:34 -0400 [thread overview]
Message-ID: <dcd393ee-daba-6fe3-9020-9594f123276a@cornell.edu> (raw)
In-Reply-To: <f67248ca-8e26-41f1-f683-72f0a1c50c4b@cornell.edu>
On 5/14/2016 9:36 PM, Ken Brown wrote:
> Commit b73e525, as corrected by commit 4639bc9, causes the test
> make-ipv4-tcp-server-with-unspecified-port in
> test/lisp/net/network-streams-tests.el to fail with the error
>
> Invalid argument 4 of operation `open-network-stream'.
>
> What happens is that make-network-process calls
> set_network_socket_coding_system, which calls open-network-stream with
> service eq t, which leads to the error in a way that I haven't sorted out.
I didn't get that last step right. The error is generated by
Ffind_operation_coding_system when it is called by
CALLN (Ffind_operation_coding_system,
Qopen_network_stream, name, p->buffer,
host, service)
in set_network_socket_coding_system.
Ken
next prev parent reply other threads:[~2016-05-15 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 1:36 bug#23540: 25.1.50; make-ipv4-tcp-server-with-unspecified-port fails Ken Brown
2016-05-15 12:16 ` Ken Brown [this message]
2016-05-15 16:15 ` Eli Zaretskii
2016-05-15 17:08 ` Ken Brown
2016-05-24 15:09 ` Ken Brown
2016-05-24 15:27 ` Eli Zaretskii
2019-10-23 10:32 ` Lars Ingebrigtsen
2019-10-23 16:31 ` bug#23508: " Ken Brown
2019-10-24 11:48 ` 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=dcd393ee-daba-6fe3-9020-9594f123276a@cornell.edu \
--to=kbrown@cornell.edu \
--cc=23540@debbugs.gnu.org \
--cc=larsi@gnus.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.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).