[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#760902: marked as done (libc6: ld-linux-x86-64.so.2 segfaults with LD_BIND_NOW=yes on some binaries generated by golang)



Your message dated Thu, 17 Dec 2015 19:48:20 +0100
with message-id <20151217184820.GA15718@aurel32.net>
and subject line Bug#710521: "ldd -r /usr/bin/go" segfaults
has caused the Debian Bug report #710521,
regarding libc6: ld-linux-x86-64.so.2 segfaults with LD_BIND_NOW=yes on some binaries generated by golang
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
710521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710521
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: aptly
Version: 0.5-4
Severity: normal

Dear Maintainer,
 I was curious about aptly and hence installed it. While installing it
came across the following :-

$ sudo aptitude install aptly
The following NEW packages will be installed:
  aptly
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,703 kB of archives. After unpacking 9,068 kB will be used.
Get: 1 http://debian.ec.as6453.net/debian/ unstable/main aptly amd64
0.5-4 [1,703 kB]
Fetched 1,703 kB in 48s (35.1 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
D000001: ensure_diversions: new, (re)loading
D000001: ensure_statoverrides: new, (re)loading
Selecting previously unselected package aptly.
(Reading database ... 561585 files and directories currently installed.)
Preparing to unpack .../archives/aptly_0.5-4_amd64.deb ...
D000001: process_archive oldversionstatus=not installed
Unpacking aptly (0.5-4) ...
D000001: process_archive updating info directory
D000001: generating infodb hashfile
Processing triggers for debian-security-support (2014.07.31) ...
D000001: cmpversions a='0:1.17.13' b='0:1.16' r=1
D000001: cmpversions a='0:1.17.13' b='0:1.16' r=1
D000001: ensure_diversions: same, skipping
Processing triggers for man-db (2.6.7.1-1) ...
D000001: ensure_diversions: same, skipping
D000001: ensure_diversions: new, (re)loading
Setting up aptly (0.5-4) ...
D000001: deferred_configure updating conffiles
ldd -r: failed at /usr/bin/adequate line 812, <$ldd> line 4.
E: Problem executing scripts DPkg::Post-Invoke 'adequate --help
>/dev/null 2>&1 || exit 0; DEBIAN_FRONTEND=readline exec adequate
--debconf --user nobody --pending'
E: Sub-process returned an error code
Failed to perform requested operation on package.  Trying to recover:
D000001: ensure_diversions: new, (re)loading

The relevant error seems to be at

ldd -r: failed at /usr/bin/adequate line 812, <$ldd> line 4.
E: Problem executing scripts DPkg::Post-Invoke 'adequate --help
>/dev/null 2>&1 || exit 0; DEBIAN_FRONTEND=readline exec adequate
--debconf --user nobody --pending'
E: Sub-process returned an error code
Failed to perform requested operation on package.  Trying to recover:
D000001: ensure_diversions: new, (re)loading

I use adequate to figure out issues with packages and those options
help make sure that the errors are known without my screen glowing and
things like that.

Please let me know if any more information is needed from my end.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'testing-updates'), (1,
'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aptly depends on:
ii  libc6  2.19-10

aptly recommends no packages.

aptly suggests no packages.

-- no debconf information
-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

--- End Message ---
--- Begin Message ---
Version: eglibc/2.19-1

On 2013-05-31 17:35, Jakub Wilk wrote:
> Package: libc6
> Version: 2.17-3
> 
> Running "ldd -r" on /usr/bin/go (shipped by golang-go 2:1.1-1) causes a
> segfault:
> 
> $ ldd -r /usr/bin/go
> 	linux-gate.so.1 (0xf7757000)
> 	libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7738000)
> 	libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf75c3000)
> 	/lib/ld-linux.so.2 (0xf7758000)
> /usr/bin/ldd: line 116:  8528 Segmentation fault      LD_TRACE_LOADED_OBJECTS=1 LD_WARN=yes LD_BIND_NOW=yes LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= "$@"

I can reproduce the problem with eglibc 2.18-4, but not with 2.19-1 and
later versions. I therefore believe the problem has been fixed and I am
closing the bug with this mail.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---

Reply to: