unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Lluís Batlle i Rossell" <viric@viric.name>
Cc: 13958@debbugs.gnu.org
Subject: bug#13958: Failing net-db.test on armv5tel glibc 2.17
Date: Fri, 15 Mar 2013 12:14:21 +0100	[thread overview]
Message-ID: <87ppz0ykxe.fsf@gnu.org> (raw)
In-Reply-To: <20130314140337.GE14560@vicerveza.homeunix.net> ("Lluís Batlle i Rossell"'s message of "Thu, 14 Mar 2013 15:03:37 +0100")

Hi Lluís!

Lluís Batlle i Rossell <viric@viric.name> skribis:

> running the test below, I see on glibc-2.17 armv5tel-linux:
> ----
> Running net-db.test
>
> ;;; (err -11)
> unexpected error code: -11 "System error"
> FAIL: net-db.test: getaddrinfo: no name
> ----

Does it happen in a chroot without /etc/resolv.conf & co.?

Is it a dynamically-linked binary?

Could you run “strace -o log -f ./check-guile net-db.test” and post
the log?

(Note that I build it with Guix on x86_64-linux-gnu without any
problems; glibc 2.17 as well, and in a chroot.)


Now, we have a problem with the ‘getaddrinfo-error’ API: EAI_SYSTEM
means “check what errno says”, and we don’t provide the errno value.

This could be fixed by passing the errno as an additional parameter to
‘throw’.  However, that would lead to wrong-num-args for existing
handlers upon EAI_SYSTEM, and would essentially force programmers to use
‘case-lambda’ for their handlers.

OTOH, there are only two occurrences of EAI_SYSTEM in inet/getaddrinfo.c
in glibc: one is for NETDB_INTERNAL, and the other is for
IDNA_DLOPEN_ERROR.  When that happens, the extra bit of information
provided by errno is probably not very helpful.

Thoughts?

Ludo’.





  reply	other threads:[~2013-03-15 11:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130310225811.GO14560@vicerveza.homeunix.net>
     [not found] ` <87txoert3q.fsf@gnu.org>
2013-03-14 14:03   ` bug#13958: Failing net-db.test on armv5tel glibc 2.17 Lluís Batlle i Rossell
2013-03-15 11:14     ` Ludovic Courtès [this message]
2013-03-15 11:34       ` Lluís Batlle i Rossell
2013-03-15 13:36         ` Ludovic Courtès
2013-03-15 13:40           ` Lluís Batlle i Rossell
2013-03-15 13:48             ` Ludovic Courtès
2013-03-25 21:47               ` Ludovic Courtès

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ppz0ykxe.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=13958@debbugs.gnu.org \
    --cc=viric@viric.name \
    /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.
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).