https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #11 from zephyrus00jp <ishik...@yk.rim.or.jp> --- I thought I posted a followup early this October, but funny, it did not seem to have made it to the bugzilla. OK, here it goes. I still cannot run Thunderbird mail client under valgrind as normal user. I get very mysterious segmentation error of valgrind. *HOWEVER*, to my surprise, when I ran valgrind as a *LOGGED IN SUPERUSER* (|su| does not work. I have to log in as superuser either from login screen or sshing to the local PC box as root.), I can run thunderbird under valgrind. successfully (!) I wonder why. So now, I have been testing thunderbird under valgrind by "ssh"ing to my local PC box after enabling superuser login of ssh daemon (which is usually off for security reasons). Anyone has any idea why this is so? >From the look of log trace, the mysterious segmentation error (as normal user) that kills valgrind occurs at the time the stack seems to be extended. (I looked at signal handling and it looks that way.) At that point, valgrind as normal user is killed, but as properly logged in superuser, the stack gets enlarged properly and the thunderbird proceeds fine under valgrind. I mention that Debian GNU/Linux kernel 3.19.5 had no problem running thunderbird under valgrind. However I have no idea how that particular kernel version with the particular kernel config had any looser restriction regarding user process trying to extend stack when it overflows. I thought stack extension is automatic under Debian as long as user sets the stack maximum size reasonably large. I set ulimit to the maximum (no limit). So my processshould be able to extend the stack as normal user under OS management, was what I thought. Does anyone have idea how to enable the reliable stack growth as ordinary user under Debian? Or maybe this is valgrind-specific stack exntesion issue under certain kernel config (including security mechanism?). I have been testing thunderbird under valgrind as superuser for a couple of weeks after long time, but use of ssh and the permission of files created as superuser during the execution of valgrind+thunderbird have made it rather awkward in the debug cycle and I really wish to use valgrind + thunderbird as normal user. Any hints/tips will be appreciated. valgrind is very useful. I already have found two clear-cut uninitialized memory access bugs that have crept in the code over the years. I suspect more to come ... TIA -- You are receiving this mail because: You are watching all bug changes.
