https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #8 from zephyrus00jp <ishik...@yk.rim.or.jp> --- Created attachment 104470 --> https://bugs.kde.org/attachment.cgi?id=104470&action=edit A log of valgrind experiencing SIGSEGV under 4.9.x kernel: with full vlgrind options This log is obtained by running valgrind under a wrapper called run-valgrind (of my creation). This wrapper runs valgrind with suitable parameters to monitor thunderbird binary as follows. valgrind --trace-children=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --trace-children-skip=/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=$HOME/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --trace-syscalls=yes /NREF-COMM-CENTRAL/objdir-tb3/dist/bin/thunderbird-bin The process IDs that appear are: pid 28538: the binary wrapper run-valgrind pid 28539: from the wrapper valgrind is executed by calling system() library call. [pid 28539] execve("/bin/sh", ["sh", "-c", "valgrind --trace-children=yes --"...], [/* 65 vars */]) = 0 pid 28540: from the spawned shell valgrind is run [pid 28540] execve("/usr/local/bin/valgrind", ["valgrind", "--trace-children=yes", "--fair-sched=yes", "--smc-check=all-non-file", "--gen-suppressions=all", "--vex-iropt-register-updates=all"..., "--child-silent-after-fork=yes", "--trace-children-skip=/usr/bin/h"..., "--num-transtab-sectors=24", "--tool=memcheck", "--freelist-vol=500000000", "--redzone-size=128", "--px-default=allregs-at-mem-acce"..., "--px-file-backed=unwindregs-at-m"..., "--malloc-fill=0xA5", "--free-fill=0xC3", "--num-callers=50", "--suppressions=/home/ishikawa/Dr"..., "--show-mismatched-frees=no", "--show-possibly-lost=no", "--read-inline-info=yes", "--trace-syscalls=yes", "/NREF-COMM-CENTRAL/objdir-tb3/di"...], [/* 65 vars */] <unfinished ...> Near the end of the log, we see the following two lines: [pid 28540] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xffeffa1fc} --- [pid 28540] +++ killed by SIGSEGV +++ So it is pid 28540 that gets killed by SIGSEGV: pid 28540 is for /usr/local/bin/valgrind thus invoked. There are two PCs which I cannot easily access all the time. Sorry for slightly different file layout on two PCs. TIA PS: I am trying to create a valgrind-enabled thunderbird binary on mozilla's compilation farm. But I have hit some unexpected difficulties for now. (The particular CPU farm does NOT have valgrind headers. Ugh.) I am trying to have it installed. Stay tuned. The series of patches AND parameters that I use to create comm-central thunderbird is captured in a few shell scripts, but they are rather complex and need customization: I am not quire sure if I can simply post the shell script and people to modify it to their environment. I may not be available for consultation always. So I thought creating a binary on a shared computer is much better. -- You are receiving this mail because: You are watching all bug changes.
