https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #12 from zephyrus00jp <ishik...@yk.rim.or.jp> --- Great news. After so many months actually a few years of mysterious valgrind crash under Debian GNU/Linux 64-bit when I tried to run thunderbird (TB) client, today, I tested the operation with this combination. ishikawa@ip030:/home/ishikawa$ valgrind --version valgrind-3.16.1 ishikawa@ip030:/home/ishikawa$ uname -a Linux ip030 5.10.0-4-amd64 #1 SMP Debian 5.10.19-1 (2021-03-02) x86_64 GNU/Linux ishikawa@ip030:/home/ishikawa$ A surprize. I could run TB under valgrind without the mysterious crashes so far. But one thing is for sure, where I would have gotten the segmentation error after signal catch presumably for extending stack, now I see a strange pipe error. Maybe previously valgrind died as ordinary user with the error related to this message, but I am not sure. Anyway, this is a real progress and I will report any more issue with the use of valgrind and TB. But I have to tell you that the memory pressure with the new valgrind and TB combination is much more pronounced. I allocate 16GB of memory to Debian GNU/Linux image in a virtualbox that runs under windows 10 (the host has 32GB). But now it is causing much paging/swapping and sometimes, the whole virtualbox does not respond for a while. Still, being able to run valgrind + TB is great improvement. I have a feeling valgrind 3.16 had a few internal improvements and linux 5.10.1 released by Debian must have a kernel feature that is valgrind friendly when valgrind needs to deal with a huge binary like TB. Thank you agian for releasing the great program to wide community of users. Happy Hacking! -- You are receiving this mail because: You are watching all bug changes.
