Oddly enough the aforementioned port's makefile doesn't have USE_WXNEEDED = yes 
. After enabling this, and trying to build, configure fails with a ./conftest 
triggering WX. mount -uo wxallowed /usr/obj allows it to build. However, in 
accord with the bug #40 for valgrind-openbsd at the maintainers bitbucket [1] , 
ktrace shows MMAP failing an allocation with errno 12. However, some discussing 
for Linux on the valgrind bugzilla shows that this failure could be 
attributable to an rlimit policy that not strictly necessary. [2] Commenting 
out the offending line of code, as suggested by [2], causes valgrind to appear 
to run normally. This line of code is still present today in valgrinds truck, 
so perhaps this fix is a workaround. Attached please find the patch.

[1] - 
https://bitbucket.org/uebayasi/valgrind-openbsd/issues/40/mmap-failure-cannot-allocate-memory-on
[2] - https://bugs.kde.org/show_bug.cgi?id=357833

Attachment: patch-coregrind_m_main_c
Description: Binary data

Reply via email to