Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
On Sat, Aug 19, 2017 at 11:58:09AM +0200, Andreas Beckmann wrote: > > terminate called after throwing an instance of 'std::logic_error' > > what(): basic_string::_M_construct null not valid > > Could this be related to #871275 "libapt-pkg5.0: requires rebuild > against GCC 7 and symbols/shlibs bump" which was fixed recently in apt? > IIRC this started after making gcc-7 the default ... I'll look if there > are new occurrences of this bug. Unlikely that it is related to this symbol change as it is a single symbol related to URIs, which apt uses while acquiring files, but at the stage packages are installed nothing worries about URIs anymore… A core dump would really be handy. It could still be a problem with gcc or perhaps dpkg changed slightly a log message and apt stumbles over parsing it correctly (althrough, dpkg wasn't uploaded in a while)… or… construction of a std::string's is done all over the place, implicit and explicit, so without details we can't even guess sensibly. Can't really suggest debugging options either, as most of them include the construction of std::string's which could easily hide the problem – and the debug usually involves stuff happening before/after dpkg is called, usually not while it's running, but oh well, we could try -o Debug::pkgDPkgProgressReporting=1 perhaps – that is heavy on string operations through, so that could turn out to be more confusing than helping… (and as said, dpkg hasn't changed in a while). Best regards David Kalnischkies signature.asc Description: PGP signature
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
control: forcemerge 871275 -1 On 2017-08-19 11:58, Andreas Beckmann wrote: > > terminate called after throwing an instance of 'std::logic_error' > > what(): basic_string::_M_construct null not valid > > Could this be related to #871275 "libapt-pkg5.0: requires rebuild > against GCC 7 and symbols/shlibs bump" which was fixed recently in apt? > IIRC this started after making gcc-7 the default ... I'll look if there > are new occurrences of this bug. Ok, I am merging the two bugs. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
> terminate called after throwing an instance of 'std::logic_error' > what(): basic_string::_M_construct null not valid Could this be related to #871275 "libapt-pkg5.0: requires rebuild against GCC 7 and symbols/shlibs bump" which was fixed recently in apt? IIRC this started after making gcc-7 the default ... I'll look if there are new occurrences of this bug. Andreas
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
Control: severity -1 important On 2017-08-19 10:29, Aurelien Jarno wrote: > Any news about this? This bug now blocks the migration of glibc to > testing. Downgrading. Andreas
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
On 2017-08-16 11:54, Aurelien Jarno wrote: > On 2017-08-16 02:41, Andreas Beckmann wrote: > > [ adding apt@, therefore quoting fully ] > > > > On 2017-08-15 22:56, Aurelien Jarno wrote: > > > control: tag - 1 + help > > > control: tag - 1 + moreinfo > > > > > > On 2017-08-15 09:58, Andreas Beckmann wrote: > > >> Package: libc-bin > > >> Version: 2.24-14 > > >> Severity: serious > > >> User: debian...@lists.debian.org > > >> Usertags: piuparts > > >> > > >> Hi, > > >> > > >> during several tests with piuparts in sid I noticed spurious and > > >> unreproducible errors while processing libc-bin triggers. > > >> Often apt-get just exits with an error code (but no error message > > >> at all) after processing the triggers. > > >> A few times I also get an error message about an uncaught exception. > > >> These failures usually go away after rerunning the test. > > >> > > >> >From the attached log (scroll to the bottom...): > > >> > > >> Processing triggers for libc-bin (2.24-14) ... > > >> terminate called after throwing an instance of 'std::logic_error' > > >> what(): basic_string::_M_construct null not valid > > > > > > What make you think it's an issue in libc-bin? The trigger processing > > > code just does: > > > > > > if [ "$1" = "triggered" ] || [ "$1" = "configure" ]; then > > > ldconfig || ldconfig --verbose > > > exit 0 > > > fi > > > > > > And there is no C++ code in ldconfig. Moreover even if ldconfig fails > > > the error is ignored and the install should not stop. > > > > OK, that probably leaves dpkg (no C++ either) and apt-get as the call > > chain to the trigger processing ... adding apt@ to the loop. > > #871275 could be a candidate, i.e. a g++7 rebuild might fix it. > > > > I reran the test where I attached the logfile yesterday repeatedly for > > 100 times with no failure. But I could probably dig out a dozen of > > similar failures from other piuparts tests. (These failures will be > > retried frequently, so will eventually succeed.) > > > > If there is some way to get more debug output for this problem, I could > > enable that globally in my piuparts instance. > > I guess you can try to get a core dump. Just make sure that you run > "ulimit -c unlimited" before running the command. The core dump will > tell you which binary actually has the issue and should provide more > info about the issue. Any news about this? This bug now blocks the migration of glibc to testing. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
On 2017-08-16 02:41, Andreas Beckmann wrote: > [ adding apt@, therefore quoting fully ] > > On 2017-08-15 22:56, Aurelien Jarno wrote: > > control: tag - 1 + help > > control: tag - 1 + moreinfo > > > > On 2017-08-15 09:58, Andreas Beckmann wrote: > >> Package: libc-bin > >> Version: 2.24-14 > >> Severity: serious > >> User: debian...@lists.debian.org > >> Usertags: piuparts > >> > >> Hi, > >> > >> during several tests with piuparts in sid I noticed spurious and > >> unreproducible errors while processing libc-bin triggers. > >> Often apt-get just exits with an error code (but no error message > >> at all) after processing the triggers. > >> A few times I also get an error message about an uncaught exception. > >> These failures usually go away after rerunning the test. > >> > >> >From the attached log (scroll to the bottom...): > >> > >> Processing triggers for libc-bin (2.24-14) ... > >> terminate called after throwing an instance of 'std::logic_error' > >> what(): basic_string::_M_construct null not valid > > > > What make you think it's an issue in libc-bin? The trigger processing > > code just does: > > > > if [ "$1" = "triggered" ] || [ "$1" = "configure" ]; then > > ldconfig || ldconfig --verbose > > exit 0 > > fi > > > > And there is no C++ code in ldconfig. Moreover even if ldconfig fails > > the error is ignored and the install should not stop. > > OK, that probably leaves dpkg (no C++ either) and apt-get as the call > chain to the trigger processing ... adding apt@ to the loop. > #871275 could be a candidate, i.e. a g++7 rebuild might fix it. > > I reran the test where I attached the logfile yesterday repeatedly for > 100 times with no failure. But I could probably dig out a dozen of > similar failures from other piuparts tests. (These failures will be > retried frequently, so will eventually succeed.) > > If there is some way to get more debug output for this problem, I could > enable that globally in my piuparts instance. I guess you can try to get a core dump. Just make sure that you run "ulimit -c unlimited" before running the command. The core dump will tell you which binary actually has the issue and should provide more info about the issue. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
[ adding apt@, therefore quoting fully ] On 2017-08-15 22:56, Aurelien Jarno wrote: > control: tag - 1 + help > control: tag - 1 + moreinfo > > On 2017-08-15 09:58, Andreas Beckmann wrote: >> Package: libc-bin >> Version: 2.24-14 >> Severity: serious >> User: debian...@lists.debian.org >> Usertags: piuparts >> >> Hi, >> >> during several tests with piuparts in sid I noticed spurious and >> unreproducible errors while processing libc-bin triggers. >> Often apt-get just exits with an error code (but no error message >> at all) after processing the triggers. >> A few times I also get an error message about an uncaught exception. >> These failures usually go away after rerunning the test. >> >> >From the attached log (scroll to the bottom...): >> >> Processing triggers for libc-bin (2.24-14) ... >> terminate called after throwing an instance of 'std::logic_error' >> what(): basic_string::_M_construct null not valid > > What make you think it's an issue in libc-bin? The trigger processing > code just does: > > if [ "$1" = "triggered" ] || [ "$1" = "configure" ]; then > ldconfig || ldconfig --verbose > exit 0 > fi > > And there is no C++ code in ldconfig. Moreover even if ldconfig fails > the error is ignored and the install should not stop. OK, that probably leaves dpkg (no C++ either) and apt-get as the call chain to the trigger processing ... adding apt@ to the loop. #871275 could be a candidate, i.e. a g++7 rebuild might fix it. I reran the test where I attached the logfile yesterday repeatedly for 100 times with no failure. But I could probably dig out a dozen of similar failures from other piuparts tests. (These failures will be retried frequently, so will eventually succeed.) If there is some way to get more debug output for this problem, I could enable that globally in my piuparts instance. Andreas
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
control: tag - 1 + help control: tag - 1 + moreinfo On 2017-08-15 09:58, Andreas Beckmann wrote: > Package: libc-bin > Version: 2.24-14 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during several tests with piuparts in sid I noticed spurious and > unreproducible errors while processing libc-bin triggers. > Often apt-get just exits with an error code (but no error message > at all) after processing the triggers. > A few times I also get an error message about an uncaught exception. > These failures usually go away after rerunning the test. > > >From the attached log (scroll to the bottom...): > > Processing triggers for libc-bin (2.24-14) ... > terminate called after throwing an instance of 'std::logic_error' > what(): basic_string::_M_construct null not valid What make you think it's an issue in libc-bin? The trigger processing code just does: if [ "$1" = "triggered" ] || [ "$1" = "configure" ]; then ldconfig || ldconfig --verbose exit 0 fi And there is no C++ code in ldconfig. Moreover even if ldconfig fails the error is ignored and the install should not stop. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers
Package: libc-bin Version: 2.24-14 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during several tests with piuparts in sid I noticed spurious and unreproducible errors while processing libc-bin triggers. Often apt-get just exits with an error code (but no error message at all) after processing the triggers. A few times I also get an error message about an uncaught exception. These failures usually go away after rerunning the test. >From the attached log (scroll to the bottom...): Processing triggers for libc-bin (2.24-14) ... terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_M_construct null not valid cheers, Andreas gcal-common_3.6.3-3.log.gz Description: application/gzip
