This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug network/10652] getaddrinfo causes segfault if multithreaded and linked statically
- From: "horst at schirmeier dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 17 Aug 2017 10:47:13 +0000
- Subject: [Bug network/10652] getaddrinfo causes segfault if multithreaded and linked statically
- Auto-submitted: auto-generated
- References: <bug-10652-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=10652
Horst Schirmeier <horst at schirmeier dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |horst at schirmeier dot com
--- Comment #25 from Horst Schirmeier <horst at schirmeier dot com> ---
This bug is still reproducible in 2.23(-r4, Gentoo) and 2.24(-9ubuntu2.2,
Ubuntu 17.04).
What I really don't get is that it even crashes if I protect calls to
gethostbyname() with a pthread mutex. However, if I call gethostbyname()
alternatingly in two different threads (2s delay between each call, one thread
1s behind the other), I could not observe crashes.
Either way, the link-time
warning: Using 'getaddrinfo' in statically linked applications requires at
runtime the shared libraries from the glibc version used for linking
should be severely upgraded to something like the following until this bug is
fixed:
warning: Using 'getaddrinfo' in statically linked applications requires at
runtime the shared libraries from the glibc version used for linking, and may
fail in spectacular ways in combination with pthreads when not yet fully
understood additional conditions hold
--
You are receiving this mail because:
You are on the CC list for the bug.