Control: reassign -1 libc6 Control: retitle -1 libc6: ld-linux-x86-64.so.2 segfaults with LD_BIND_NOW=yes on some binaries generated by golang On Tue, 2014-09-09 at 09:16 +0200, Sébastien Delafond wrote: > Apparently this is actually a problem with adequate, and not aptly. See > for instance 706915[1], 707080[2], and 707091[3]. > > Apparently upgrading to adequate 0.5.2 and libc6 (and friends) 2.17-2 > should fix it, if I read those aforementioned bug reports correctly. Confirmed with strace that this is caused by a SIGSEGV in libc6 in the following packages: aptly heartbleeder golang-go.tools These command-lines cause a segfault: LD_BIND_NOW=yes /usr/bin/aptly LD_BIND_NOW=yes /usr/bin/heartbleeder LD_BIND_NOW=yes /usr/bin/present LD_BIND_NOW=yes /usr/bin/godoc LD_BIND_NOW=yes /usr/bin/updater LD_BIND_NOW=yes /usr/bin/builder Interestingly the issue doesn't happen with docker.io and some of the other executables in golang-go.tools even though they are written in Go. shirish शिरीष: btw if you see this issue with adequate again, please don't file the bug against the package or adequate but against libc6. The way to reproduce similar problems is to run these commands (replace aptly by the command name) and report any segfaults: ldd /usr/bin/aptly ldd -r /usr/bin/aptly LD_VERBOSE= LD_BIND_NOW=yes LD_WARN=yes LD_TRACE_LOADED_OBJECTS=1 /usr/bin/aptly -- bye, pabs http://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part