[valgrind] [Bug 398545] Support for SHA instruction on Ryzen

2018-09-12 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=398545 --- Comment #3 from Tom Hughes --- Well the most obvious would be because nobody has submitted an implementation yet... If that's an AMD specific instruction then in general I'm not sure we have anything much in the way of support for those - not sure

[valgrind] [Bug 398545] Support for SHA instruction on Ryzen

2018-09-12 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=398545 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes

[valgrind] [Bug 398178] cachegrind --LL=5242880,2,64 command parameter for Opteron 6174 rejected

2018-09-04 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=398178 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #2 from Tom Hughes

[valgrind] [Bug 397393] valgrind: the 'impossible' happened: (Archlinux)

2018-08-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=397393 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu Resolution

[valgrind] [Bug 397012] glibc ld.so uses arch_prctl on i386

2018-08-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=397012 Tom Hughes changed: What|Removed |Added CC||subhranilmukherjee190@gmail

[valgrind] [Bug 396887] arch_prctl should return EINVAL on unknown option

2018-08-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=396887 Tom Hughes changed: What|Removed |Added CC||subhranilmukherjee190@gmail

[valgrind] [Bug 397393] valgrind: the 'impossible' happened: (Archlinux)

2018-08-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=397393 --- Comment #2 from Tom Hughes --- *** This bug has been marked as a duplicate of bug 396887 *** -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 396887] arch_prctl should return EINVAL on unknown option

2018-08-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=396887 Tom Hughes changed: What|Removed |Added CC||drankinatty@suddenlinkmail

[valgrind] [Bug 397521] valgrind: the 'impossible' happened: Unsupported arch_prctl option

2018-08-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=397521 --- Comment #2 from Tom Hughes --- *** This bug has been marked as a duplicate of bug 396887 *** -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 397012] glibc ld.so uses arch_prctl on i386

2018-08-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=397012 Tom Hughes changed: What|Removed |Added CC||drankinatty@suddenlinkmail

[valgrind] [Bug 397521] valgrind: the 'impossible' happened: Unsupported arch_prctl option

2018-08-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=397521 Tom Hughes changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC

[valgrind] [Bug 388786] Support bpf syscall in amd64 Linux

2018-08-14 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=388786 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu Resolution

[valgrind] [Bug 397357] symbols not loaded with binutils-2.31.1 unless -fuse-ld=gold specified to gcc/g++

2018-08-11 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=397357 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #2 from Tom Hughes

[valgrind] [Bug 395682] Reading debug info of binaries with readonly PT_LOAD segments

2018-07-11 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=395682 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #8 from Tom Hughes

[valgrind] [Bug 396415] Valgrind is not looking up $ORIGIN rpath of shebang programs

2018-07-11 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=396415 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes

[valgrind] [Bug 396220] vex x86->IR: unhandled instruction bytes: 0xC4 0xE2 0x41 0xF7

2018-07-05 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=396220 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #2 from Tom Hughes

[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6

2018-07-04 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=396176 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu Resolution

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

2018-07-04 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=353370 Tom Hughes changed: What|Removed |Added CC||cj-...@zougloub.eu --- Comment #20 from Tom

[valgrind] [Bug 395871] vex amd64->IR: unhandled instruction bytes: 0xF 0x3 0xC0 0x48 0x25 0xFF 0xF 0x0

2018-06-25 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=395871 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu Summary|unhandled

[valgrind] [Bug 381556] arm64: Handle feature registers access on 4.11 Linux kernel or later

2018-06-18 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=381556 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #9 from Tom Hughes

[valgrind] [Bug 395434] valgrind XML output should setlinebuf() to facilitate online use

2018-06-15 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=395434 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes

[valgrind] [Bug 395246] vex amd64->IR: unhandled instruction bytes:

2018-06-11 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=395246 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes

[valgrind] [Bug 395136] valgrind: m_syswrap/syswrap-main.c:438 (Bool eq_SyscallStatus(UInt, SyscallStatus *, SyscallStatus *)): the 'impossible' happened.

2018-06-08 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=395136 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu Summary|Valgrind

[valgrind] [Bug 392855] valgrind reports 1 additional allocation and 1024 additional bytes allocated (again...)

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=392855 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Status|REOPENED|RESOLVED Reso

[valgrind] [Bug 369030] WARNING: unhandled amd64-linux syscall: 171 (setdomainname)

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=369030 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

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

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=369028 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 369027] WARNING: unhandled amd64-linux syscall: 216 (remap_file_pages)

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=369027 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 369030] WARNING: unhandled amd64-linux syscall: 171 (setdomainname)

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=369030 --- Comment #3 from Tom Hughes <t...@compton.nu> --- I see no sign that this has been added. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 369031] WARNING: unhandled amd64-linux syscall: 308 (setns)

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=369031 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 368960] WARNING: unhandled amd64-linux syscall: 163 (acct)

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=368960 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 369032] WARNING: unhandled amd64-linux syscall: 205 (set_thread_area)

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=369032 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 369033] WARNING: unhandled amd64-linux syscall: 139 (sysfs)

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=369033 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 369026] WARNING: unhandled amd64-linux syscall: 169 (reboot)

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=369026 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 369034] WARNING: unhandled amd64-linux syscall: 136 (ustat)

2018-04-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=369034 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 393272] allow to not reuse freed memory

2018-04-18 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=393272 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 387940] amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0x89 0x44 (__x86_rdrand)

2018-04-18 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=387940 --- Comment #4 from Tom Hughes <t...@compton.nu> --- As this is your own code the most likely cause is that you have compiled with -march=native or similar, which is never a good idea when using valgrind as we are not always up to date with the

[valgrind] [Bug 387940] amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0x89 0x44 (__x86_rdrand)

2018-04-18 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=387940 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Reso

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

2018-04-18 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=353370 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||ezy...@mit.edu --- Comme

[valgrind] [Bug 393083] Unimplemented fcntl

2018-04-13 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=393083 --- Comment #1 from Tom Hughes <t...@compton.nu> --- Can you please run with --trace-syscalls=yes and paste in the last few lines leading up to the error? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 393083] Unimplemented fcntl

2018-04-13 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=393083 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Summary|NOT IMPLEMENTED |Unimplemented

[valgrind] [Bug 392855] valgrind reports 1 additional allocation and 1024 additional bytes allocated (again...)

2018-04-08 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=392855 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Resolution|--- |INVALID

[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, mdir_el1)

2018-03-29 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=392146 --- Comment #6 from Tom Hughes <t...@compton.nu> --- I think you were already told on IRC when you asked that it should provide results which reflect the capabilities of the emulated environment, which in at least some cases is likely t

[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

2018-03-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384230 --- Comment #16 from Tom Hughes <t...@compton.nu> --- Were not actually daft you know and I did check the Intel manual multiple times. To be clear I believe this quote covers it: "The address-size override prefix (67H) allows programs to swi

[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

2018-03-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384230 --- Comment #14 from Tom Hughes <t...@compton.nu> --- Not really - the actual bogus instruction was in ld.so which is not part of the code generated by that compilation. So you would need to isolate the relevant file in the glibc source a

[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

2018-03-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384230 --- Comment #12 from Tom Hughes <t...@compton.nu> --- I don't believe anybody has a test case so there wouldn't be any point. If you can come up some C that will cause the compiler to generate this sequence then please feel free to report it. -

[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

2018-03-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384230 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 390765] Stack traces given by Memcheck aren't helpful

2018-02-20 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=390765 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 390498] Valgrind reports errors without full backtrace on arm64

2018-02-15 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=390498 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 390471] suppression by specification of source-file line number

2018-02-14 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=390471 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Reso

[valgrind] [Bug 389470] Redirection of index function in ld.so.1 breaks compatibility on old environments

2018-01-26 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=389470 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@comp

[valgrind] [Bug 388847] WARNING: unhandled arm64-linux syscall: 168 (getcpu)

2018-01-12 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=388847 --- Comment #3 from Tom Hughes <t...@compton.nu> --- No that's completely different - that's just valgrind doing it's job and telling you that your program is passing uninitialised data to a system call. -- You are receiving this mail becaus

[valgrind] [Bug 388847] WARNING: unhandled arm64-linux syscall: 168 (getcpu)

2018-01-12 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=388847 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 388847] WARNING: unhandled arm64-linux syscall: 168 (getcpu)

2018-01-12 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=388847 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@comp

[valgrind] [Bug 388706] warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0xf2

2018-01-08 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=388706 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Summary|Long bunches of warnings: |w

[valgrind] [Bug 388706] Long bunches of warnings: "warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0xf2

2018-01-08 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=388706 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@comp

[valgrind] [Bug 388603] ARM Advanced SIMD vfma.f32 with Q or D registers reports unsupported instruction

2018-01-05 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=388603 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 388493] exp-sgcheck fails on DW_TAG_subrange_type

2018-01-03 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=388493 --- Comment #2 from Tom Hughes <t...@compton.nu> --- To be honest I think here are probably two entirely separate issues. One is the DWARF parser not handling the subrange tag: parse DIE(readdwarf3.c:3619): confused by: <2><17a1ec>:

[valgrind] [Bug 388493] exp-sgcheck fails on DW_TAG_subrange_type

2018-01-03 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=388493 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 388407] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x29

2018-01-01 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=388407 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Resolution|--- |DUPLICATE

[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

2018-01-01 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384230 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||sdel...@sdelang.fr --- C

[valgrind] [Bug 387664] Memcheck: make expensive-definedness-checks be the default

2017-12-07 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=387664 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

2017-12-04 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384230 --- Comment #6 from Tom Hughes <t...@compton.nu> --- Because we still don't really understand what that instruction means - that patch is just a best guess at how to decode it. If that patch is correct then the prefix is redundant in which ca

[valgrind] [Bug 208052] strlcpy error when n = 0

2017-11-14 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=208052 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@comp

[valgrind] [Bug 386115] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xD3 0x8B any program

2017-10-23 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=386115 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Reso

[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

2017-10-23 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384230 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||hartb...@gmail.com --- C

[valgrind] [Bug 385707] memcheck-amd64-linux crashing

2017-10-13 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=385707 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 384732] posix_spawn with glibc 2.25 causes an assertion

2017-09-15 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384732 --- Comment #5 from Tom Hughes <t...@compton.nu> --- We already detect CLONE_VFORK|CLONE_VM as a special case and deliberately drop CLONE_VM because I imagine anything else would be a disaster as valgrind's shadow memory etc would be

[valgrind] [Bug 384732] posix_spawn with glibc 2.25 causes an assertion

2017-09-15 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384732 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

2017-09-01 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384230 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Attachment #107621|0 |1 is ob

[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

2017-08-31 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=384230 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-07-12 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #9 from Tom Hughes <t...@compton.nu> --- Actually that's not the same at all - in fact it's not even a bug (in valgrind) it's just a normal error report about a bug in your program where it is passing uninitialised data to a syste

[valgrind] [Bug 381819] amd64: unhandled instruction bytes: 0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4 0x0 0x0 0x89

2017-06-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=381819 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@comp

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-06-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=381815 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 381769] Use ucontext_t instead of struct ucontext

2017-06-28 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=381769 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu Atta

[valgrind] [Bug 380193] vex x86->IR: unhandled instruction bytes: 0xC5 0xFB 0x2C 0x40 while running Memcheck on mencoder

2017-05-25 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=380193 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 380037] valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD

2017-05-20 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=380037 --- Comment #2 from Tom Hughes <t...@compton.nu> --- By the way the specific problem you're seeing here is that asan is trying to make sure it's intercepting malloc etc but of course valgrind also wants to do the same thing and they can't both

[valgrind] [Bug 380037] valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD

2017-05-20 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=380037 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 379966] WARNING: unhandled amd64-linux syscall: 313 (finit_module)

2017-05-18 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=379966 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Summary|WARNING: unhandled syscall: |WARNING: unh

[valgrind] [Bug 379966] WARNING: unhandled syscall: 313 (finit_module)

2017-05-18 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=379966 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

2017-05-15 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #8 from Tom Hughes <t...@compton.nu> --- Fails at 32Gb without patch: trying for 31 GB .. ==12078== Warning: set address range perms: large range [0x3960c040, 0x7f960c040) (defined) .. OK ==12078== Warning: set address range perms:

[valgrind] [Bug 379537] Client requests can't be used in C++11 constexpr functions

2017-05-05 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=379537 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu --- Comm

[valgrind] [Bug 331126] Compiling with mipsbe toolchain

2017-04-20 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=331126 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 378892] Unhandled amd64-linux syscall: 324 [membarrier]

2017-04-17 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=378892 --- Comment #1 from Tom Hughes <t...@compton.nu> --- This appears to be membarrier and should be fairly simple to support. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 378892] Unhandled amd64-linux syscall: 324 [membarrier]

2017-04-17 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=378892 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@comp

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

2017-03-27 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=353370 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||juliusde...@gma

[valgrind] [Bug 378180] Unrecognised instruction in std::mt19937 constructor

2017-03-27 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=378180 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@comp

[valgrind] [Bug 351692] Dumps created by valgrind are not readable by gdb

2017-03-17 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=351692 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 376142] Segfaults on MIPS Cavium Octeon boards

2017-03-14 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=376142 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 344524] store conditional of guest applications always fail - observed on Octeon3(MIPS)

2017-03-14 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=344524 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 375514] valgrind_get_tls_addr() does not work in case of static TLS

2017-03-14 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=375514 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@compton.nu -

[valgrind] [Bug 341481] MIPS64: Iop_CmpNE32 triggers false warning on MIPS64 platforms

2017-03-14 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=341481 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 376870] unhandled amd64-darwin syscall: unix:446

2017-02-23 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=376870 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@comp

[valgrind] [Bug 376869] unhandled syscall: 531

2017-02-23 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=376869 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@comp

[valgrind] [Bug 376279] disInstr(arm64): unhandled instruction 0xD50320FF

2017-02-11 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=376279 Tom Hughes <t...@compton.nu> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 376279] disInstr(arm64): unhandled instruction 0xD50320FF

2017-02-10 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=376279 --- Comment #4 from Tom Hughes <t...@compton.nu> --- Created attachment 103953 --> https://bugs.kde.org/attachment.cgi?id=103953=edit Proposed patch Here's suggested patch that just ignores unknown HINT instructions. Untested as yet...

[valgrind] [Bug 376279] disInstr(arm64): unhandled instruction 0xD50320FF

2017-02-10 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=376279 --- Comment #3 from Tom Hughes <t...@compton.nu> --- Indeed objdump disassembles in as hint #0x7: db78: d11b43ffsub sp, sp, #0x6d0 db7c: a9007bfdstp x29, x30, [sp] db80: 910003fdmov

[valgrind] [Bug 376279] disInstr(arm64): unhandled instruction 0xD50320FF

2017-02-10 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=376279 --- Comment #1 from Tom Hughes <t...@compton.nu> --- Full log is in the output of the koji build that triggered it (this package runs valgrind as part of it's own tests): https://kojipkgs.fedoraproject.org//work/tasks/8288/17708288/build.log -

[valgrind] [Bug 376279] disInstr(arm64): unhandled instruction 0xD50320FF

2017-02-10 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=376279 --- Comment #2 from Tom Hughes <t...@compton.nu> --- This appears to be a HINT instruction, but with an immediate value of 111 which is unallocated according to the manual I'm looking at. Now that should mean it's treated as a NOP but I wond

[valgrind] [Bug 376279] New: disInstr(arm64): unhandled instruction 0xD50320FF

2017-02-10 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=376279 Bug ID: 376279 Summary: disInstr(arm64): unhandled instruction 0xD50320FF Product: valgrind Version: 3.12.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED

[valgrind] [Bug 375845] Unrecognised instruction using std::random_device

2017-02-01 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=375845 Tom Hughes <t...@compton.nu> changed: What|Removed |Added CC||t...@comp

  1   2   >