[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-19 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #15 from Paul Floyd --- Please could you move discusssion here: https://github.com/paulfloyd/freebsd_valgrind/issues/174 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #14 from serpent7...@gmail.com --- I attached log with debug tcmalloc version. Is using sbrk normal? Isn't this a legacy thing? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #13 from serpent7...@gmail.com --- Created attachment 143745 --> https://bugs.kde.org/attachment.cgi?id=143745=edit Running swipl under valgrind with debug tcmalloc -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #12 from serpent7...@gmail.com --- I attached log with added --track-origins=yes -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #11 from serpent7...@gmail.com --- Created attachment 143736 --> https://bugs.kde.org/attachment.cgi?id=143736=edit Running swipl under valgrind with track-origins enabled -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-18 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=445607 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-18 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #9 from Paul Floyd --- Does --track-origins=yes show anything useful? What is happening here pl_thread_idle2_va (src/pl-alloc.c:1899) ? ==59737== Thread 2 gc: ==59737== Conditional jump or move depends on uninitialised value(s) ==59737==

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-18 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #8 from serpent7...@gmail.com --- I did a build in a jail to not mess up my system, hope this isn't an issue. I built valgrind at f13667b1eff8d3d06590683b9981ced611bd3c69 + brk change and debug build of swi-pl 8.2.3. I've attached log from

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-18 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #7 from serpent7...@gmail.com --- Created attachment 143711 --> https://bugs.kde.org/attachment.cgi?id=143711=edit Russing swi-pl under valgrind (with debug symbols) -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-18 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #6 from Paul Floyd --- My mistake /usr/local/lib/libtcmalloc_minimal.so.4.5.9 is google perftools tcmalloc https://www.freshports.org/devel/google-perftools/ Try getting a debug build of swi-pl first. If there is a problem it is more

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-18 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #5 from serpent7...@gmail.com --- OK, but how can I build debug version of jemallloc and then use it? As I understand it, it is FreeBSD's malloc? Do I run make in /usr/src/lib/libc/stdlib/jemalloc? -- You are receiving this mail because:

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #4 from Paul Floyd --- I've pushed the change to resolve the missing syscall wrapper. Can you clone and build Valgrind (with the diff in my previous message) and also build debug versions of swi-pl and jemallloc? I'll also try to get in

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #3 from Paul Floyd --- If I increase the brk segment from 8M to 1G that part of the message goes away, but the other parts remain. The diff to do that is diff --git a/coregrind/m_initimg/initimg-freebsd.c

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #2 from Paul Floyd --- I've done a super quick implementation of clock_getcpuclockid2 [it probably needs a separate i386 version because the 1st param is 64bits]. I now get paulf> ./vg-in-place

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=445607 --- Comment #1 from Paul Floyd --- Looking at syscalls.master the missing syscall wrapper seems fairly straightforward 247 AUE_NULLSTD { int clock_getcpuclockid2( id_t id, int which,

[valgrind] [Bug 445607] Unhandled amd64-freebsd syscall: 247

2021-11-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=445607 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr CC|