I've added more context to https://bugs.debian.org/1059352#38, but just to have
some info here too this is the error:

722s ==221367== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
722s ==221367== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright 
info
722s ==221367== Command: /usr/bin/apt-get update -o Acquire::Queue-Mode=access
722s ==221367== 
722s ==221367== 
722s ==221367== Process terminating with default action of signal 11 (SIGSEGV)
722s ==221367==  Access not within mapped region at address 0xFE7F2A9C
722s ==221367==    at 0x4938838: ReadMessages(int, 
std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, 
std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, 
std::char_traits<char>, std::allocator<char> > > >&) (in 
/usr/lib/arm-linux-gnueabihf/libapt-pkg.so.6.0.0)
722s ==221367==  If you believe this happened as a result of a stack
722s ==221367==  overflow in your program's main thread (unlikely but
722s ==221367==  possible), you can try to increase the size of the
722s ==221367==  main thread stack using the --main-stacksize= flag.
722s ==221367==  The main thread stack size used in this run was 8388608.
722s ==221367== 
722s ==221367== HEAP SUMMARY:
722s ==221367==     in use at exit: 119,915 bytes in 1,882 blocks
722s ==221367==   total heap usage: 11,673 allocs, 9,791 frees, 868,849 bytes 
allocated
722s ==221367== 
722s ==221367== LEAK SUMMARY:
722s ==221367==    definitely lost: 0 bytes in 0 blocks
722s ==221367==    indirectly lost: 0 bytes in 0 blocks
722s ==221367==      possibly lost: 0 bytes in 0 blocks
722s ==221367==    still reachable: 119,915 bytes in 1,882 blocks
722s ==221367==         suppressed: 0 bytes in 0 blocks
722s ==221367== Rerun with --leak-check=full to see details of leaked memory
722s ==221367== 
722s ==221367== For lists of detected and suppressed errors, rerun with: -s
722s ==221367== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 42821 from 
965)
722s Segmentation fault
722s FAIL: exitcode 139

Reply via email to