NSS is unreliable in statically linked binaries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GLibC |
Incomplete
|
Medium
|
|||
glibc (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
More in https:/
I'm getting following on amd64 as well as arm64:
Thread 3 "drone" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f9a7b2090 (LWP 21950)]
0x0000007f98ddd334 in internal_getent (stream=
buffer=0xca8e08 "gethostbyname4_r", buffer@
herrnop@
251 nss_files/
(gdb) bt
#0 0x0000007f98ddd334 in internal_getent (stream=
buffer=0xca8e08 "gethostbyname4_r", buffer@
herrnop@
#1 0x0000007f98dde2c0 in _nss_files_
errnop=
#2 0x0000000000a71438 in gaih_inet ()
#3 0x0000000000a72ef0 in getaddrinfo ()
#4 0x00000000009b1bec in _cgo_7a2d42f1a3
#5 0x000000000047cf28 in runtime.asmcgocall () at /home/go/
#6 0x00000044201716c0 in ?? ()
#7 0x0000000000000001 in ?? ()
Changed in glibc: | |
importance: | Unknown → Medium |
status: | Unknown → Incomplete |
summary: |
- SIGSEGV on internal_getent nss_files/files-XXX.c:251 + NSS is unreliable in statically linked binaries |
Status changed to 'Confirmed' because the bug affects multiple users.