https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #13 from zephyrus00jp ---
Created attachment 123636
--> https://bugs.kde.org/attachment.cgi?id=123636=edit
uname -a output, and other requested logs.
Thank you for the comment.
I stand corrected. I think valgrind works in the context of
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #12 from John Reiser ---
Please run "uname -a" then copy+paste the entire output, and label with the
circumstances (3 cases: normal user, logged-in root, su from normal user to
root).
It's not obvious which kernels are being used today.
--
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #11 from zephyrus00jp ---
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
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #10 from zephyrus00jp ---
(In reply to John Reiser from comment #9)
> It looks to me like some part of the problem arises when memcheck is working
> on the driver for the video graphics card. This suggests a cause
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #9 from John Reiser ---
It looks to me like some part of the problem arises when memcheck is working on
the driver for the video graphics card. This suggests a cause for
non-determinism, and also a reason for
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #8 from zephyrus00jp ---
Created attachment 104470
--> https://bugs.kde.org/attachment.cgi?id=104470=edit
A log of valgrind experiencing SIGSEGV under 4.9.x kernel: with full vlgrind
options
This log is obtained by
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #7 from zephyrus00jp ---
To avoid the uncertainty about how mozilla thunderbird is compiled for valgrind
testing, I will create a binary (for valgrind testing) on mozilla's tryserver.
(You an see that what patches are
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #6 from zephyrus00jp ---
Created attachment 104426
--> https://bugs.kde.org/attachment.cgi?id=104426=edit
A log to show valgrind with --vex-iropt-register-updates=all still segfaults
(under 4.7.0.1)
Sorry I was not
https://bugs.kde.org/show_bug.cgi?id=377006
John Reiser changed:
What|Removed |Added
CC||jrei...@bitwagon.com
---
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #4 from zephyrus00jp ---
Created attachment 104424
--> https://bugs.kde.org/attachment.cgi?id=104424=edit
log of segfault failure under 4.9.x series kernel (debian). with
--trace-syscalls=yes
This is under 4.9.x.
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #3 from zephyrus00jp ---
Description of log directory archive.
[1] Description of log files under 4.7.0.1
There are a group of files. (N being 2,3,4,5)
- logN-main.txt,
- logN-gdb-.txt,
- logN-gdb-'.txt
-
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #2 from zephyrus00jp ---
Created attachment 104264
--> https://bugs.kde.org/attachment.cgi?id=104264=edit
Log for 3.19.5 (sucessful runs for comparison)
I needed to remove the largest log which contains a much
https://bugs.kde.org/show_bug.cgi?id=377006
--- Comment #1 from zephyrus00jp ---
Created attachment 104263
--> https://bugs.kde.org/attachment.cgi?id=104263=edit
Log for 4.9.x kernel test runs
Log of test runs under 4.9.x kernel.
--
You are receiving this mail
13 matches
Mail list logo