[valgrind] [Bug 371396] helgrind and drd pth_cond_destroy_busy testcase hang with new glibc cond var implementation

https://bugs.kde.org/show_bug.cgi?id=371396 --- Comment #1 from Mark Wielaard --- A workaround (skip the test if a newer glibc is detected) has been checked in as valgrind r16097. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 371396] New: helgrind and drd pth_cond_destroy_busy testcase hang with new glibc cond var implementation

https://bugs.kde.org/show_bug.cgi?id=371396 Bug ID: 371396 Summary: helgrind and drd pth_cond_destroy_busy testcase hang with new glibc cond var implementation Product: valgrind Version: 3.12 SVN Platform: Other

[valgrind] [Bug 358213] helgrind/drd bar_bad testcase hangs or crashes with new glibc pthread barrier implementation

https://bugs.kde.org/show_bug.cgi?id=358213 Mark Wielaard changed: What|Removed |Added Summary|helgrind/drd bar_bad|helgrind/drd bar_bad

[valgrind] [Bug 370265] ISA 3.0 HW cap stuff needs updating

https://bugs.kde.org/show_bug.cgi?id=370265 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 370265] ISA 3.0 HW cap stuff needs updating

https://bugs.kde.org/show_bug.cgi?id=370265 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 369356] pre_mem_read_sockaddr syscall wrapper can crash with bad sockaddr

https://bugs.kde.org/show_bug.cgi?id=369356 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 369356] pre_mem_read_sockaddr syscall wrapper can crash with bad sockaddr

https://bugs.kde.org/show_bug.cgi?id=369356 --- Comment #2 from Mark Wielaard --- valgrind svn r15990 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 369359] msghdr_foreachfield can crash when handling bad iovec

https://bugs.kde.org/show_bug.cgi?id=369359 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 369360] Bad sigprocmask old or new sets can crash valgrind

https://bugs.kde.org/show_bug.cgi?id=369360 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 369361] vmsplice syscall wrapper crashes on bad iovec

https://bugs.kde.org/show_bug.cgi?id=369361 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 369362] Bad sigaction arguments crash valgrind

https://bugs.kde.org/show_bug.cgi?id=369362 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 369383] x86 sys_modify_ldt wrapper crashes on bad ptr

https://bugs.kde.org/show_bug.cgi?id=369383 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 369402] Bad set/get_thread_area pointer crashes valgrind

https://bugs.kde.org/show_bug.cgi?id=369402 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 369441] bad lvec argument crashes process_vm_readv/writev syscall wrappers

https://bugs.kde.org/show_bug.cgi?id=369441 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 369446] valgrind crashes on unknown fcntl command

https://bugs.kde.org/show_bug.cgi?id=369446 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #9 from Mark Wielaard --- (In reply to Ivo Raisr from comment #8) > the new test case works ok (I am able to simulate the problem on Solaris) > with 'make one component inaccessible'. Thanks for testing. Lets go with this

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

https://bugs.kde.org/show_bug.cgi?id=369175 --- Comment #30 from Mark Wielaard --- (In reply to Carl Love from comment #29) > Please review the patch and let me know if you see any issues. If everyone > approves the patch and the ISA 3.0 Big endian test passes, I will commit

[valgrind] [Bug 369446] valgrind crashes on unknown fcntl command

https://bugs.kde.org/show_bug.cgi?id=369446 --- Comment #1 from Mark Wielaard --- Created attachment 101322 --> https://bugs.kde.org/attachment.cgi?id=101322=edit Don't crash, but warn and return EINVAL on unknown fcntl command. -- You are receiving this mail because: You

[valgrind] [Bug 369446] New: valgrind crashes on unknown fcntl command

https://bugs.kde.org/show_bug.cgi?id=369446 Bug ID: 369446 Summary: valgrind crashes on unknown fcntl command Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity:

[valgrind] [Bug 369441] New: bad lvec argument crashes process_vm_readv/writev syscall wrappers

https://bugs.kde.org/show_bug.cgi?id=369441 Bug ID: 369441 Summary: bad lvec argument crashes process_vm_readv/writev syscall wrappers Product: valgrind Version: unspecified Platform: Other OS: Linux

[valgrind] [Bug 369441] bad lvec argument crashes process_vm_readv/writev syscall wrappers

https://bugs.kde.org/show_bug.cgi?id=369441 --- Comment #1 from Mark Wielaard --- Created attachment 101321 --> https://bugs.kde.org/attachment.cgi?id=101321=edit Don't check bad iovec array in process_vm_readv/writev. The TODO comment already said what to do. -- You are

[valgrind] [Bug 369409] null pointer dereference in vgPlain_do_syscall

https://bugs.kde.org/show_bug.cgi?id=369409 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #7 from Mark Wielaard --- Created attachment 101309 --> https://bugs.kde.org/attachment.cgi?id=101309=edit new nocwd testcase How about this variant of the test. It tries a couple of things to make sure getcwd will fail.

[valgrind] [Bug 369402] Bad set/get_thread_area pointer crashes valgrind

https://bugs.kde.org/show_bug.cgi?id=369402 --- Comment #1 from Mark Wielaard --- Created attachment 101307 --> https://bugs.kde.org/attachment.cgi?id=101307=edit linux-x86 check get/set_thread_area pointer before use. -- You are receiving this mail because: You are watching

[valgrind] [Bug 369402] New: Bad set/get_thread_area pointer crashes valgrind

https://bugs.kde.org/show_bug.cgi?id=369402 Bug ID: 369402 Summary: Bad set/get_thread_area pointer crashes valgrind Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED

[valgrind] [Bug 369383] x86 sys_modify_ldt wrapper crashes on bad ptr

https://bugs.kde.org/show_bug.cgi?id=369383 --- Comment #1 from Mark Wielaard --- Created attachment 101298 --> https://bugs.kde.org/attachment.cgi?id=101298=edit Fix crash in sys_modify_ldt wrapper on bad ptr. Make sure ptr is safe_to_deref if not NULL. Also fixup some

[valgrind] [Bug 369383] New: x86 sys_modify_ldt wrapper crashes on bad ptr

https://bugs.kde.org/show_bug.cgi?id=369383 Bug ID: 369383 Summary: x86 sys_modify_ldt wrapper crashes on bad ptr Product: valgrind Version: 3.12 SVN Platform: Other OS: Linux Status: UNCONFIRMED

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

https://bugs.kde.org/show_bug.cgi?id=369175 --- Comment #21 from Mark Wielaard --- Created attachment 101296 --> https://bugs.kde.org/attachment.cgi?id=101296=edit Patch to wrap _BCDstring128_helper address in fnptr_to_fnentry After some debugging Julian suggested this fix.

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

https://bugs.kde.org/show_bug.cgi?id=369175 --- Comment #20 from Mark Wielaard --- Created attachment 101295 --> https://bugs.kde.org/attachment.cgi?id=101295=edit Trace for smaller badness2 reproducer Trace output for a smaller reproducer: $ cat badness2.c #include

[valgrind] [Bug 369362] Bad sigaction arguments crash valgrind

https://bugs.kde.org/show_bug.cgi?id=369362 --- Comment #1 from Mark Wielaard --- Created attachment 101290 --> https://bugs.kde.org/attachment.cgi?id=101290=edit Fix crash in linux [rt_]sigaction wrapper with bad old/new sigaction handler. Since we try to modify the old/new

[valgrind] [Bug 369362] New: Bad sigaction arguments crash valgrind

https://bugs.kde.org/show_bug.cgi?id=369362 Bug ID: 369362 Summary: Bad sigaction arguments crash valgrind Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity:

[valgrind] [Bug 369361] vmsplice syscall wrapper crashes on bad iovec

https://bugs.kde.org/show_bug.cgi?id=369361 --- Comment #1 from Mark Wielaard --- Created attachment 101289 --> https://bugs.kde.org/attachment.cgi?id=101289=edit Fix crash in vmsplice linux kernel wrapper when iovec is bad -- You are receiving this mail because: You are

[valgrind] [Bug 369361] New: vmsplice syscall wrapper crashes on bad iovec

https://bugs.kde.org/show_bug.cgi?id=369361 Bug ID: 369361 Summary: vmsplice syscall wrapper crashes on bad iovec Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED

[valgrind] [Bug 369360] Bad sigprocmask old or new sets can crash valgrind

https://bugs.kde.org/show_bug.cgi?id=369360 --- Comment #1 from Mark Wielaard --- Created attachment 101288 --> https://bugs.kde.org/attachment.cgi?id=101288=edit Fix crash when old/new sigprocmask isn't safe to dereference Since we want to use the set and oldset for

[valgrind] [Bug 369360] New: Bad sigprocmask old or new sets can crash valgrind

https://bugs.kde.org/show_bug.cgi?id=369360 Bug ID: 369360 Summary: Bad sigprocmask old or new sets can crash valgrind Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED

[valgrind] [Bug 369359] msghdr_foreachfield can crash when handling bad iovec

https://bugs.kde.org/show_bug.cgi?id=369359 --- Comment #1 from Mark Wielaard --- Created attachment 101287 --> https://bugs.kde.org/attachment.cgi?id=101287=edit Fix crash in msghdr_foreachfield when iov_len isn't safe to dereference. Also stop checking when max length of

[valgrind] [Bug 369359] New: msghdr_foreachfield can crash when handling bad iovec

https://bugs.kde.org/show_bug.cgi?id=369359 Bug ID: 369359 Summary: msghdr_foreachfield can crash when handling bad iovec Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED

[valgrind] [Bug 369356] pre_mem_read_sockaddr syscall wrapper can crash with bad sockaddr

https://bugs.kde.org/show_bug.cgi?id=369356 --- Comment #1 from Mark Wielaard --- Created attachment 101286 --> https://bugs.kde.org/attachment.cgi?id=101286=edit Fix pre_mem_read_sockaddr crash on invalid syscall arguments Don't do any more checks if it isn't safe to inspect

[valgrind] [Bug 369356] New: pre_mem_read_sockaddr syscall wrapper can crash with bad sockaddr

https://bugs.kde.org/show_bug.cgi?id=369356 Bug ID: 369356 Summary: pre_mem_read_sockaddr syscall wrapper can crash with bad sockaddr Product: valgrind Version: unspecified Platform: Other OS: Linux

[valgrind] [Bug 369264] Fedora 24 i686 and vex x86->IR: unhandled instruction bytes: 0xC5 0xF8 0x10 0x3

https://bugs.kde.org/show_bug.cgi?id=369264 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #5 from Mark Wielaard --- (In reply to Ivo Raisr from comment #4) > So this simple change fixes the warning: > - execlp ("echo", "echo", "Hello", "World", NULL); > + execlp ("echo", "echo", "Hello", "World", (char *)

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

https://bugs.kde.org/show_bug.cgi?id=369175 --- Comment #17 from Mark Wielaard --- Since some of the output looks as if we jump into (or just read from?) the ODP and that gives a permission error/SEGV, could you provide the section and segments of the tool to double check

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

https://bugs.kde.org/show_bug.cgi?id=369175 --- Comment #18 from Mark Wielaard --- Never mind the objdump -h gives the right information. The 0x3824B2B0 is indeed in the middle of the ODP. The ODP is loaded and DATA (not CODE), which I assume means it is readable (so we can

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

https://bugs.kde.org/show_bug.cgi?id=369175 --- Comment #9 from Mark Wielaard --- Assuming that is with remote vgdb attached then you should be able to get the generated IR and assembly with: monitor v.translate 0x100016dc 0b0011 (See the manual or valgrind

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

https://bugs.kde.org/show_bug.cgi?id=369175 --- Comment #6 from Mark Wielaard --- (In reply to Julian Seward from comment #3) > I tried to reproduce this on gcc112.fsffrance.org (a P8 system) but failed -- > it runs OK. I'd be happy to chase this if I could reproduce on a

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 Mark Wielaard changed: What|Removed |Added CC||iv...@ivosh.net,

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #1 from Mark Wielaard --- Created attachment 101237 --> https://bugs.kde.org/attachment.cgi?id=101237=edit Don't require the current working directory to exist. At startup valgrind fetches the current working directory

[valgrind] [Bug 369209] New: valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 Bug ID: 369209 Summary: valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist. Product: valgrind Version: 3.12 SVN Platform: Other

[valgrind] [Bug 368419] Perf Events ioctls not implemented

https://bugs.kde.org/show_bug.cgi?id=368419 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 357932] vex amd64->IR: unhandled instruction bytes: 0xF2 0x49 0xF 0x5D and 0xF2 0x49 0xF 0x5F

https://bugs.kde.org/show_bug.cgi?id=357932 --- Comment #4 from Mark Wielaard --- Or maybe Julian means the "redundant" REXB is altering the e register field and so it needs further adjustment to get the correct register if REXB is set. Anyway, a testcase and how to (or what)

[valgrind] [Bug 357932] vex amd64->IR: unhandled instruction bytes: 0xF2 0x49 0xF 0x5D and 0xF2 0x49 0xF 0x5F

https://bugs.kde.org/show_bug.cgi?id=357932 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 368120] x86_linux asm _start functions do not keep 16-byte aligned stack pointer

https://bugs.kde.org/show_bug.cgi?id=368120 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

https://bugs.kde.org/show_bug.cgi?id=369169 --- Comment #6 from Mark Wielaard --- (In reply to Carl Love from comment #5) > Please test the patch and see if the regression test results are as expected > on your machine. They PASS. Thanks. -- You are receiving this mail

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

https://bugs.kde.org/show_bug.cgi?id=369175 --- Comment #1 from Mark Wielaard --- Note that running the program itself (not under valgrind) seems fine. It is only when ran under valgrind that it produces the SIGSEGV: ==28394== Process terminating with default action of signal

[valgrind] [Bug 369175] New: jm_vec_isa_2_07 test crashes on ppc64

https://bugs.kde.org/show_bug.cgi?id=369175 Bug ID: 369175 Summary: jm_vec_isa_2_07 test crashes on ppc64 Product: valgrind Version: 3.12 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

https://bugs.kde.org/show_bug.cgi?id=369169 --- Comment #4 from Mark Wielaard --- The diffs are the same because the none/tests/ppc64/jm_int_isa_2_07.stdout.exp and none/tests/ppc64/jm_int_isa_2_07.stdout.exp-LE expect files are the same. -- You are receiving this mail

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

https://bugs.kde.org/show_bug.cgi?id=369169 --- Comment #3 from Mark Wielaard --- Created attachment 101220 --> https://bugs.kde.org/attachment.cgi?id=101220=edit diff with LE expected output -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

https://bugs.kde.org/show_bug.cgi?id=369169 --- Comment #2 from Mark Wielaard --- Created attachment 101219 --> https://bugs.kde.org/attachment.cgi?id=101219=edit diff with expected output -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

https://bugs.kde.org/show_bug.cgi?id=369169 --- Comment #1 from Mark Wielaard --- Created attachment 101218 --> https://bugs.kde.org/attachment.cgi?id=101218=edit test output -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 369169] New: ppc64 fails jm_int_isa_2_07 test

https://bugs.kde.org/show_bug.cgi?id=369169 Bug ID: 369169 Summary: ppc64 fails jm_int_isa_2_07 test Product: valgrind Version: 3.12 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal

[valgrind] [Bug 339596] AMD64 xop instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=339596 Bug 339596 depends on bug 369000, which changed state. Bug 369000 Summary: AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9 https://bugs.kde.org/show_bug.cgi?id=369000

[valgrind] [Bug 369000] AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=369000 Mark Wielaard changed: What|Removed |Added Blocks||369053 -- You are receiving

[valgrind] [Bug 339596] AMD64 xop instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=339596 Mark Wielaard changed: What|Removed |Added Depends on||369053 -- You are receiving

[valgrind] [Bug 369053] New: AMD64 fma4 instructions missing 256 bit support

https://bugs.kde.org/show_bug.cgi?id=369053 Bug ID: 369053 Summary: AMD64 fma4 instructions missing 256 bit support Product: valgrind Version: 3.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity:

[valgrind] [Bug 339596] AMD64 xop instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=339596 Mark Wielaard changed: What|Removed |Added Blocks|369000 | Depends on|

[valgrind] [Bug 369000] AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=369000 Mark Wielaard changed: What|Removed |Added Depends on|339596 | Blocks|

[valgrind] [Bug 358213] helgrind/drd bar_bad testcase hangs with new glibc pthread barrier implementation

https://bugs.kde.org/show_bug.cgi?id=358213 --- Comment #6 from Mark Wielaard --- I checked in a workaround for the hang based on the attachement as valgrind svn r15962. This does make sure that the tests don't hang indefenitely. But they do introduce (more) non-determinism

[valgrind] [Bug 369000] AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=369000 --- Comment #3 from Mark Wielaard --- VEX svn r3249 and valgrind svn r15961 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 369000] AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=369000 --- Comment #2 from Mark Wielaard --- Created attachment 101170 --> https://bugs.kde.org/attachment.cgi?id=101170=edit Testcases for fma4 instructions. This is an extension of the testcases for the fma4 instructions I wrote for bug

[valgrind] [Bug 369000] AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=369000 --- Comment #1 from Mark Wielaard --- Created attachment 101169 --> https://bugs.kde.org/attachment.cgi?id=101169=edit Implement AMD FMA4 instructions. This is just the FMA4 part of the patch proposed in bug #339596. The original

[valgrind] [Bug 339596] AMD64 xop instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=339596 Mark Wielaard changed: What|Removed |Added Summary|AMD64 fma4 and xop |AMD64 xop instructions

[valgrind] [Bug 339596] AMD64 fma4 and xop instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=339596 Mark Wielaard changed: What|Removed |Added Blocks||369000 -- You are receiving

[valgrind] [Bug 369000] New: AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=369000 Bug ID: 369000 Summary: AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9 Product: valgrind

[valgrind] [Bug 355188] valgrind should intercept all malloc related global functions by default

https://bugs.kde.org/show_bug.cgi?id=355188 Mark Wielaard changed: What|Removed |Added CC||y...@tsoft.com --- Comment #6

[valgrind] [Bug 368861] Please make valgrind work with programs using google-perftools malloc library

https://bugs.kde.org/show_bug.cgi?id=368861 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com

[valgrind] [Bug 322935] disInstr(arm): unhandled instruction: 0xF1010200, valgrind: Unrecognised instruction on Raspbian

https://bugs.kde.org/show_bug.cgi?id=322935 --- Comment #34 from Mark Wielaard --- (In reply to Peter Maydell from comment #33) > (In reply to Mark Wielaard from comment #32) > > valgrind should already intercept the memcmp from glibc. This one however is > > in a different

[valgrind] [Bug 322935] disInstr(arm): unhandled instruction: 0xF1010200, valgrind: Unrecognised instruction on Raspbian

https://bugs.kde.org/show_bug.cgi?id=322935 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 364948] Add IBM ISA 3.0 support, patch set 5

https://bugs.kde.org/show_bug.cgi?id=364948 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 359503] Add missing syscalls for aarch64 (arm64)

https://bugs.kde.org/show_bug.cgi?id=359503 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 368791] unhandled syscall: 167

https://bugs.kde.org/show_bug.cgi?id=368791 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 368791] unhandled amd64-linux syscall: 167 (swapon)

https://bugs.kde.org/show_bug.cgi?id=368791 Mark Wielaard changed: What|Removed |Added Summary|unhandled syscall: 167 |unhandled amd64-linux

[valgrind] [Bug 361726] WARNING:unhandled syscall on ppc64 and amd64 (membarrier)

https://bugs.kde.org/show_bug.cgi?id=361726 --- Comment #6 from Mark Wielaard --- BTW. This is an awesome overview of all the linux syscalls by architectures: https://fedora.juszkiewicz.com.pl/syscalls.html -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 361726] WARNING:unhandled syscall on ppc64 and amd64 (membarrier)

https://bugs.kde.org/show_bug.cgi?id=361726 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1

[valgrind] [Bug 358620] ARM: disInstr(arm): unhandled instruction: 0xF1010200

https://bugs.kde.org/show_bug.cgi?id=358620 Mark Wielaard changed: What|Removed |Added Summary|ARM: unhandled syscall: 357 |ARM: disInstr(arm):

[valgrind] [Bug 368412] False positive result for altivec capability check

https://bugs.kde.org/show_bug.cgi?id=368412 --- Comment #6 from Mark Wielaard --- Thanks, pushed as valgrind svn r15952 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 359181] Buffer Overflow during Demangling

https://bugs.kde.org/show_bug.cgi?id=359181 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 368412] False positive result for altivec capability check

https://bugs.kde.org/show_bug.cgi?id=368412 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 359181] Buffer Overflow during Demangling

https://bugs.kde.org/show_bug.cgi?id=359181 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1

[valgrind] [Bug 339596] AMD64 fma4 and xop instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=339596 Mark Wielaard changed: What|Removed |Added Summary|vex amd64->IR: unhandled|AMD64 fma4 and xop

[valgrind] [Bug 339596] vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=339596 --- Comment #19 from Mark Wielaard --- Created attachment 100956 --> https://bugs.kde.org/attachment.cgi?id=100956=edit Current stdout.diff file for new fma4.vgtest and proposed patch -- You are receiving this mail because: You are

[valgrind] [Bug 339596] vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=339596 --- Comment #18 from Mark Wielaard --- Created attachment 100955 --> https://bugs.kde.org/attachment.cgi?id=100955=edit Testcases for fma4 instructions Here are some testcases for the FMA4 instructions. I haven't looked yet at the

[valgrind] [Bug 339596] vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

https://bugs.kde.org/show_bug.cgi?id=339596 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 360571] Error about the Android Runtime reading below the stack pointer on ARM

https://bugs.kde.org/show_bug.cgi?id=360571 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com -- You are

[valgrind] [Bug 359952] Unrecognised PCMPESTRM variants

https://bugs.kde.org/show_bug.cgi?id=359952 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

[valgrind] [Bug 364413] pselect sycallwrapper mishandles NULL sigmask

https://bugs.kde.org/show_bug.cgi?id=364413 --- Comment #3 from Mark Wielaard --- I made a typo which caused: ...checking makefile consistency none/tests/Makefile.am:1: error: pselect_sigmask_null.vgtest is missing in EXTRA_DIST none/tests/Makefile.am:1: error:

[valgrind] [Bug 364413] pselect sycallwrapper mishandles NULL sigmask

https://bugs.kde.org/show_bug.cgi?id=364413 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 364413] pselect sycallwrapper mishandles NULL sigmask

https://bugs.kde.org/show_bug.cgi?id=364413 --- Comment #1 from Mark Wielaard --- Created attachment 99546 --> https://bugs.kde.org/attachment.cgi?id=99546=edit Proposed testcase and fix When the last argument ss == NULL don't check whether it is valid and don't try to copy

[valgrind] [Bug 364413] New: pselect sycallwrapper mishandles NULL sigmask

https://bugs.kde.org/show_bug.cgi?id=364413 Bug ID: 364413 Summary: pselect sycallwrapper mishandles NULL sigmask Product: valgrind Version: 3.11 SVN Platform: Other URL: https://bugzilla.redhat.com/show_bug.cgi?id=1344082

[valgrind] [Bug 363680] add renameat2() support

https://bugs.kde.org/show_bug.cgi?id=363680 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

  1   2   >