Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers

[Aurelien Jarno <aurelien@aurel32.net>]

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-qa@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
aurelien@aurel32.net                 http://www.aurel32.net