https://bugs.kde.org/show_bug.cgi?id=405295
Sam James changed:
What|Removed |Added
CC||s...@gentoo.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #13 from zephyrus00jp ---
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
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #12 from zephyrus00jp ---
Great news.
After so many months actually a few years of mysterious valgrind crash under
Debian GNU/Linux 64-bit when I tried to run thunderbird (TB) client, today, I
tested the operation with this combination.
https://bugs.kde.org/show_bug.cgi?id=405295
dan w. miller changed:
What|Removed |Added
CC||dm9426...@gmail.com
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #11 from zephyrus00jp ---
My previous comment about valgrind + thunderbird running fine as superuser
under Debian GNU/Linux may be a bit premature:
The test certainly ran some tests, but after printing the log below, valgrind
seems to get
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #10 from zephyrus00jp ---
Now I realize that where the ordinary user receives mysterious segmentation
error message (not even caught by valgrind and the remote gdb session to vgdb
of valgrind is terminated) is the following position marked
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #9 from zephyrus00jp ---
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
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #8 from zephyrus00jp ---
(In reply to zephyrus00jp from comment #7)
> This is what I found.
>
> (A side note: under
> 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 (2018-12-22) x86_64 GNU/Linux,
> I could run very old 32-bit TB 22.0a1
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #7 from zephyrus00jp ---
This is what I found.
(A side note: under
4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 (2018-12-22) x86_64 GNU/Linux,
I could run very old 32-bit TB 22.0a1 (2013-03-20)
under valgrind-3.15.0.RC1.)
However, under the
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #6 from zephyrus00jp ---
I will try to obtain the stack trace.
It is just that I am not even sure what process exactly is segfaulting, but
given that valgrind ought to be in control of all the subprocesses, it is
valgrind.
I will try my
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #5 from Julian Seward ---
(In reply to zephyrus00jp from comment #3)
> Created attachment 119027 [details]
> Log from the failed valgrind run of mozilla thunderbird (segmentation error
> somewhere)
> --15408-- REDIR: 0x4d12640
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #4 from zephyrus00jp ---
Dear Julian,
I am still trying analyze the segmentation failure which I observe
when I try to run thunderbird under valgrind.
System is Debian GNU/Linux.
Linux ip030 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #3 from zephyrus00jp ---
Created attachment 119027
--> https://bugs.kde.org/attachment.cgi?id=119027=edit
Log from the failed valgrind run of mozilla thunderbird (segmentation error
somewhere)
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #2 from zephyrus00jp ---
(In reply to Julian Seward from comment #1)
> Hi zephyrus00jp. Thanks for working on TB. I use it all the time.
>
> Try removing --read-var-info=yes from the flags. I suspect that will
> help. There's not much
https://bugs.kde.org/show_bug.cgi?id=405295
--- Comment #1 from Julian Seward ---
Hi zephyrus00jp. Thanks for working on TB. I use it all the time.
Try removing --read-var-info=yes from the flags. I suspect that will
help. There's not much loss since Memcheck hardly uses that information
15 matches
Mail list logo
