https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #13 from zephyrus00jp <ishik...@yk.rim.or.jp> --- Clarification: This is the mysterious error I see today (valgrind would have crashed before here.) ... 14:38.51 GECKO(31703) --31707-- SIGSEGV: si_code=1 faultaddr=0x1ffeff6f90 tid=1 ESP=0x1ffeff6f90 seg=0x1ffe001000-0x1ffeff6fff 14:38.51 GECKO(31703) --31707-- -> extended stack base to 0x1ffeff6000 14:38.51 GECKO(31703) --31707-- sync signal handler: signal=11, si_code=1, EIP=0x483873e, eip=0x100cd76014, from kernel 14:38.51 GECKO(31703) --31707-- SIGSEGV: si_code=1 faultaddr=0x1ffeff5ff0 tid=1 ESP=0x1ffeff5fe0 seg=0x1ffe001000-0x1ffeff5fff 14:38.51 GECKO(31703) --31707-- -> extended stack base to 0x1ffeff5000 14:41.15 GECKO(31703) --31707-- WARNING: Serious error when reading debug info 14:41.15 GECKO(31703) --31707-- When reading debug info from /memfd:mozilla-ipc (deleted): 14:41.15 GECKO(31703) --31707-- failed to stat64/stat this file 14:41.19 GECKO(31703) --31707-- WARNING: Serious error when reading debug info 14:41.19 GECKO(31703) --31707-- When reading debug info from /memfd:mozilla-ipc (deleted): 14:41.19 GECKO(31703) --31707-- failed to stat64/stat this file 14:41.62 GECKO(31703) ==31707== Warning: set address range perms: large range [0x132d88c000, 0x172d88d000) (noaccess) 17:23.24 GECKO(31703) --31707-- REDIR: 0x4930490 (libstdc++.so.6:operator delete(void*)) redirected to 0x4839e40 (operator delete(void*)) Before, mysteriously, valgrind + TB worked in a superuser account. However, as I had mentioned earlier, valgrind crashed by experincing a mysterious segfault if I tried to run valgrind with TB as an ordinary user as in comment 5 until several months ago. I gave up using valgrind for a while and tried to use ASAN as often as possible, but ASAN can't detect uninitialized value use. After so many months of not using valgrind, I tried valgrind as an ordinary user today, and it is running without the crash so far. Not needing to login as superuser and mess up file permissions all over is not quite nice. So I am very happy that valgrind + TB combination can run in ordinary user account under Debian GNU/Linux again. But like I said, I have no idea what was the problem. That "Serious error" condition I see today > 14:41.15 GECKO(31703) --31707-- WARNING: Serious error when reading debug info > 14:41.15 GECKO(31703) --31707-- When reading debug info from > /memfd:mozilla-ipc (deleted): may have caused the older version of valgrind to crash. Of course, Debian's kernel may have changed for the better. After all I could run small binary under valgrind as ordinary user without an issue under Debian GNU/linux all the while :-( -- You are receiving this mail because: You are watching all bug changes.
