https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #9 from zephyrus00jp <ishik...@yk.rim.or.jp> --- A very mysterious things happened. I could not run valgrind against locally created Thunderbird mail client binary for quite some time under Debian. A few years ago, this happened on stock GNU Debian/Linux kernel 3.1x.y series, and I found that older kernel 3.9 or something like that helped. Yes, it was kernel dependent. Ugh... I kept that kernel around for quite some time, but other developement tools and 4K display needed a newer kernel and so I ditched that kernel. I could not run valgrind+thunderbird combination for a couple of years now. Today, I tried to see if increasing the user space stack are might help. ulimit -a showed my stack size was about 13MB big, but I increased it to 16GiB by ulimit -s 16000. Still no luck. valgrind died due to mysterious segmentation error that is not even reported back to the gdb remote session when I used vgdb feature of valgrind. (This mysterious nature of the crash reported as "Segmentation Error" when I tried to run thunderbird under valgrind really puzzled me to no end since it started to appear a few years ago.) Anyway, I tried to tweak ulimit for stack size further. Then somehow the command refused. It seemed that I could not get to set it larger than 16000. I could reset it to something smaller like 15000. So I tried to invoke "su" and try running thunderbird+valgrind. Then thunderbird binary refused to run stating something to the effect of "TB does not run as superuser in normal user session": presumably due to security reasons. SO I QUIT my ordinary login, and then LOGGED IN AS ROOT USER/ S U R P R I S E ( ! ! ! ) thunderbird runs under valgrind when I ran it as logged in superuser (root) !? So it seems to me that - "Segmentation Error" is caused by some kind of security mechansim (superuser vs ordinary user restriction)? Anyway, I am about to run the whole |make mozmill| test suite of thunderbird under valgrind again. Yes, it is a bit risky to run this test under root, but I have saved patch and others into a different linux image, and so I think I can recover even if there is some serious bug in thunderbird... The security mechanism Debian my have are - APP ARMOR - SELinux - etc. But when I looked under /var/log to see if there are any relevant messages about the security mechanism kicked into abort valgrind+thunderbird, I have found nothing so far. Just a short message that thunderbird under valgrind runs as logged in superuser, but not as normal user under the latest Debian GNU/Linux kernel. This is the output from uname on the PC. Linux ip030 4.19.0-5-amd64 #1 SMP Debian 4.19.37-6 (2019-07-18) x86_64 GNU/Linux (Actually it runs inside VirtualBox.) I already see a few disturbing memory error messages from the first couple of minutes run. I hope I can find a slew of unreported errors. So this is not the most helpful report, but at least now I know how to run thunderbird under valgrind... TIA -- You are receiving this mail because: You are watching all bug changes.
