help-shishi
[Top][All Lists]
Advanced

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

Bug#835328: marked as done (shishi: Weird error while building (Serious


From: Debian Bug Tracking System
Subject: Bug#835328: marked as done (shishi: Weird error while building (Serious error when reading debug info))
Date: Wed, 24 Aug 2016 15:39:07 +0000

Your message dated Wed, 24 Aug 2016 08:38:26 -0700
with message-id <address@hidden>
and subject line Re: Bug#835328: shishi: Weird error while building (Serious 
error when reading debug info)
has caused the Debian Bug report #835328,
regarding shishi: Weird error while building (Serious error when reading debug 
info)
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 address@hidden
immediately.)


-- 
835328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835328
Debian Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: shishi: Weird error while building (Serious error when reading debug info) Date: Wed, 24 Aug 2016 15:16:36 +0200 (CEST) User-agent: Alpine 2.11 (DEB 23 2013-08-11)
Package: shishi
Version: 1.0.2-6

Dear maintainer:

Several weeks ago I tried to build this package on stretch with 
"dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build this package),
and it failed in this way:

--------------------------------------------------------------------------------
make[4]: Entering directory '/<<PKGBUILDDIR>>/tests'
--20992-- WARNING: Serious error when reading debug info
--20992-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.22.so:
--20992-- Ignoring non-Dwarf2/3/4 block in .debug_info
--20992-- WARNING: Serious error when reading debug info
--20992-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.22.so:
--20992-- Last block truncated in .debug_info; ignoring
--20992-- WARNING: Serious error when reading debug info
--20992-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.22.so:
--20992-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
==20992== Conditional jump or move depends on uninitialised value(s)
==20992==    at 0x4018D88: index (in /lib/x86_64-linux-gnu/ld-2.22.so)
==20992==    by 0x40077CC: expand_dynamic_string_token (in 
/lib/x86_64-linux-gnu/ld-2.22.so)
==20992==    by 0x400794B: fillin_rpath (in /lib/x86_64-linux-gnu/ld-2.22.so)
==20992==    by 0x40080E3: _dl_init_paths (in /lib/x86_64-linux-gnu/ld-2.22.so)
==20992==    by 0x4003097: dl_main (in /lib/x86_64-linux-gnu/ld-2.22.so)
==20992==    by 0x4016F0F: _dl_sysdep_start (in 
/lib/x86_64-linux-gnu/ld-2.22.so)
==20992==    by 0x4004C49: _dl_start (in /lib/x86_64-linux-gnu/ld-2.22.so)
==20992==    by 0x4000C97: ??? (in /lib/x86_64-linux-gnu/ld-2.22.so)
==20992==    by 0xF: ???
==20992==    by 0xFFF00063A: ???
==20992==    by 0xFFF000644: ???
==20992==    by 0xFFF00065D: ???
==20992== 
--20992-- WARNING: Serious error when reading debug info
--20992-- When reading debug info from /lib/x86_64-linux-gnu/libdl-2.22.so:
--20992-- Ignoring non-Dwarf2/3/4 block in .debug_info
--20992-- WARNING: Serious error when reading debug info
--20992-- When reading debug info from /lib/x86_64-linux-gnu/libdl-2.22.so:
--20992-- Last block truncated in .debug_info; ignoring
--20992-- WARNING: Serious error when reading debug info
--20992-- When reading debug info from /lib/x86_64-linux-gnu/libdl-2.22.so:
--20992-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--20992-- WARNING: Serious error when reading debug info
--20992-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--20992-- Ignoring non-Dwarf2/3/4 block in .debug_info
--20992-- WARNING: Serious error when reading debug info
--20992-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--20992-- Last block truncated in .debug_info; ignoring
--20992-- WARNING: Serious error when reading debug info
--20992-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--20992-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
PASS: authenticator
Makefile:1871: recipe for target 'authenticator.log' failed
make[4]: *** [authenticator.log] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/tests'
Makefile:1850: recipe for target 'check-TESTS' failed
make[3]: *** [check-TESTS] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/tests'
Makefile:2021: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/tests'
Makefile:1437: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
/usr/share/cdbs/1/class/makefile.mk:113: recipe for target 
'debian/stamp-makefile-check' failed
make: *** [debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------

I got this failure on two different Azure virtual machines, using
sbuild and eatmydata, but I can't reproduce it anymore.

I'm reporting this anyway just in case you think this may be a problem
which does worth to be investigated (maybe with the help of 
snapshot.debian.org).
If not, feel free to close the bug, as it does not seem to happen anymore.

I attach two different build logs.

Thanks.

Attachment: shishi_1.0.2-6_amd64-20160621T0136Z.gz
Description: application/gzip

Attachment: shishi_1.0.2-6_amd64-20160704T0954Z.gz
Description: application/gzip


--- End Message ---
--- Begin Message --- Subject: Re: Bug#835328: shishi: Weird error while building (Serious error when reading debug info) Date: Wed, 24 Aug 2016 08:38:26 -0700 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
Santiago Vila <address@hidden> writes:

> I got this failure on two different Azure virtual machines, using sbuild
> and eatmydata, but I can't reproduce it anymore.

> I'm reporting this anyway just in case you think this may be a problem
> which does worth to be investigated (maybe with the help of
> snapshot.debian.org).  If not, feel free to close the bug, as it does
> not seem to happen anymore.

Those are errors from valgrind (shishi runs some of its tests under
valgrind to look for memory errors).  valgrind notoriously gets out of
sync with libc or other bits of the dynamic loader and breaks like that
(which is one of the reasons why I've never turned on automated valgrind
testing for my various packages).

My guess given the timing is that this is #810295, which was fixed in
valgrind 1:3.12.0~svn20160714-1.  I'll go a head and close on that basis,
since it no longer seems to be happening.

Thank you for the report!  It's definitely useful to have reports of
issues like this in case they recur.

-- 
Russ Allbery (address@hidden)               <http://www.eyrie.org/~eagle/>

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]