[valgrind] [Bug 369029] WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)

2021-03-18 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=369029 --- Comment #20 from zephyrus00jp --- Funny, I still get this under linux amd64. > 44:03.61 GECKO(32022) --32026-- WARNING: unhandled amd64-linux syscall: 315 Doesn't valgrind 3.16.1 have this patch yet? TIA -- You are receiving this mail beca

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2021-03-16 Thread zephyrus00jp
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 seg

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2021-03-16 Thread zephyrus00jp
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

[valgrind] [Bug 369029] WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)

2020-07-26 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=369029 --- Comment #13 from zephyrus00jp --- (In reply to Mark Wielaard from comment #12) > Created attachment 130422 [details] > Cleaned up patch from bug #405394 > > (In reply to zephyrus00jp from comment #11) > > I think I need to me

[valgrind] [Bug 369029] WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)

2020-06-17 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=369029 --- Comment #11 from zephyrus00jp --- I think I need to merge the patch from 405394 into the patch here and then the patch would be complete. Let me remind myself to do this next weekend. -- You are receiving this mail because: You are watching all

[valgrind] [Bug 369029] WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)

2020-04-14 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=369029 --- Comment #7 from zephyrus00jp --- Created attachment 127556 --> https://bugs.kde.org/attachment.cgi?id=127556=edit manual page of sched_getattr and sched_setattr from Debian GNU/Linux Here is the copy of man page of the sched_geta

[valgrind] [Bug 369028] WARNING: unhandled amd64-linux syscall: 314 (sched_setattr)

2020-04-14 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=369028 zephyrus00jp changed: What|Removed |Added CC||ishik...@yk.rim.or.jp --- Comment #3 from

[valgrind] [Bug 405394] Add support for sched_setattr and sched_getattr system call.

2020-04-14 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=405394 zephyrus00jp changed: What|Removed |Added CC||ishik...@yk.rim.or.jp --- Comment #7 from

[valgrind] [Bug 369029] WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)

2020-04-14 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=369029 --- Comment #6 from zephyrus00jp --- I needed to implement the support for these two system calls because somehow I found that running thunderbird under valgrind for mozilla test suite called mochitest forced valgrind to create so many tasks (> 1

[valgrind] [Bug 369029] WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)

2020-04-14 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=369029 --- Comment #5 from zephyrus00jp --- Created attachment 127555 --> https://bugs.kde.org/attachment.cgi?id=127555=edit Log of running the test program under the patched valgrind. Log of the program. In the case of passing the structure mentio

[valgrind] [Bug 369029] WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)

2020-04-14 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=369029 --- Comment #4 from zephyrus00jp --- Created attachment 127554 --> https://bugs.kde.org/attachment.cgi?id=127554=edit A test program to test the operation of sched_getattr() and sched_setattr(). A simple program that I used to test the supp

[valgrind] [Bug 369029] WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)

2020-04-14 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=369029 --- Comment #3 from zephyrus00jp --- Created attachment 127553 --> https://bugs.kde.org/attachment.cgi?id=127553=edit Patch to support sched_getattr and sched_setattr. This is the patch for linux (x86_64) created and test under Debian GNU/Li

[valgrind] [Bug 369029] WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)

2020-04-14 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=369029 zephyrus00jp changed: What|Removed |Added CC||ishik...@yk.rim.or.jp --- Comment #2 from

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2019-10-31 Thread zephyrus00jp
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 cont

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2019-10-31 Thread zephyrus00jp
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

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2019-09-04 Thread zephyrus00jp
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

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2019-09-04 Thread zephyrus00jp
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

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2019-09-04 Thread zephyrus00jp
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

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2019-04-09 Thread zephyrus00jp
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

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2019-04-09 Thread zephyrus00jp
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

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2019-04-01 Thread zephyrus00jp
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

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2019-03-25 Thread zephyrus00jp
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 (2018-12

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2019-03-25 Thread zephyrus00jp
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:

[valgrind] [Bug 405295] valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2019-03-10 Thread zephyrus00jp
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. Ther

[valgrind] [Bug 405295] New: valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.)

2019-03-10 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=405295 Bug ID: 405295 Summary: valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.) Product: valgrind Version: 3.14.0 Platform: Other

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2017-03-14 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=377006 --- Comment #10 from zephyrus00jp <ishik...@yk.rim.or.jp> --- (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 sugg

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2017-03-09 Thread zephyrus00jp
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=edit A log of valgrind experiencing SIGSEGV under 4.9.x kernel: with full vlgrind options This log is

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2017-03-07 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=377006 --- Comment #7 from zephyrus00jp <ishik...@yk.rim.or.jp> --- 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 p

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2017-03-06 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=377006 --- Comment #6 from zephyrus00jp <ishik...@yk.rim.or.jp> --- 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)

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2017-03-06 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=377006 --- Comment #4 from zephyrus00jp <ishik...@yk.rim.or.jp> --- 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 un

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2017-02-28 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=377006 --- Comment #3 from zephyrus00jp <ishik...@yk.rim.or.jp> --- 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-ddd

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2017-02-28 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=377006 --- Comment #2 from zephyrus00jp <ishik...@yk.rim.or.jp> --- 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 contai

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2017-02-28 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=377006 --- Comment #1 from zephyrus00jp <ishik...@yk.rim.or.jp> --- 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 mai