[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 Rhys Kidd changed: What|Removed |Added CC||magda.schwa...@gmail.com --- Comment #14 from Rhys

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 Rhys Kidd changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 Chris Wilson changed: What|Removed |Added CC||chris+...@qwirx.com ---

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 lou.salk...@gmail.com changed: What|Removed |Added CC||lou.salk...@gmail.com -- You are

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 --- Comment #11 from FX --- (In reply to Rhys Kidd from comment #10) > Helpfully, there's a bug report tracking that too and a draft patch for that > at https://bugs.kde.org/show_bug.cgi?id=380269 That's what I was saying. I'm

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 --- Comment #10 from Rhys Kidd --- We know there's some low-level threading state we aren't handling properly. Sounds like you're hitting that. Helpfully, there's a bug report tracking that too and a draft patch for that at

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 --- Comment #9 from FX --- The lpq issue: with the patch from this PR, I trigger 383723. Adding the patch at 383723, I get 380269. Adding the tentative patch posted at 380269, I still get an error: ==63832== Thread 2: ==63832==

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 --- Comment #8 from Rhys Kidd --- (In reply to FX from comment #7) > ==55783== valgrind: Unrecognised instruction at address 0x1010bfd93. > ==55783==at 0x1010BFD93: _dispatch_kq_init (in > /usr/lib/system/libdispatch.dylib) >

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 --- Comment #7 from FX --- No, wrote to fast :) I found another issue: $ /tmp/bin/valgrind /usr/bin/lpq ==55783== Memcheck, a memory error detector ==55783== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 --- Comment #6 from Rhys Kidd --- (In reply to FX from comment #5) > Louis' patch fixes it for me. I've been able to run various binaries (bash, > zsh, clang, etc.) under valgrind on macOS 10.13.2 without any error. Thanks for the

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 --- Comment #5 from FX --- Louis' patch fixes it for me. I've been able to run various binaries (bash, zsh, clang, etc.) under valgrind on macOS 10.13.2 without any error. Many binaries, however, generate some messages like

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 Rhys Kidd changed: What|Removed |Added CC||therealbenwi...@gmail.com ---

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

https://bugs.kde.org/show_bug.cgi?id=385279 Rhys Kidd changed: What|Removed |Added Summary|unhandled syscall: mach:43 |[PATCH] unhandled syscall: