This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug network/17733] New: Resolver bind, getsockname namespace
- From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 19 Dec 2014 18:36:54 +0000
- Subject: [Bug network/17733] New: Resolver bind, getsockname namespace
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17733
Bug ID: 17733
Summary: Resolver bind, getsockname namespace
Product: glibc
Version: 2.21
Status: NEW
Severity: normal
Priority: P2
Component: network
Assignee: unassigned at sourceware dot org
Reporter: jsm28 at gcc dot gnu.org
On Linux architectures using socketcall, the resolver ends up bringing in
strong symbols for bind and getsockname, which are not in POSIX.1-1996; e.g.:
[initial] timer_create -> [librt.a(timer_create.o)] __active_timer_sigev_thread
-> [librt.a(timer_routines.o)] pthread_create ->
[libpthread.a(pthread_create.o)] __resp -> [libc.a(res_libc.o)] __res_iclose ->
[libc.a(res_init.o)] __if_nametoindex -> [libc.a(if_index.o)] __netlink_close
-> [libc.a(ifaddrs.o)] __bind -> [libc.a(bind.o)] bind
[initial] timer_create -> [librt.a(timer_create.o)] __active_timer_sigev_thread
-> [librt.a(timer_routines.o)] pthread_create ->
[libpthread.a(pthread_create.o)] __resp -> [libc.a(res_libc.o)] __res_iclose ->
[libc.a(res_init.o)] __if_nametoindex -> [libc.a(if_index.o)] __netlink_close
-> [libc.a(ifaddrs.o)] __getsockname -> [libc.a(getsockname.o)] getsockname
--
You are receiving this mail because:
You are on the CC list for the bug.