Sigmoid Social

Felix Palmen :freebsd: :c64:I just stress-tested the current dev state of <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#swad</a> on <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>. The first attempt failed miserably, got a lot of errors accepting a connection. Well, this lead to another little improvement, I added another static method to my logging interface that mimics <a href="https://mastodon.bsd.cafe/tags/perror" class="mention hashtag" rel="nofollow noopener" target="_blank">#perror</a>: Also print the description of the system errno. With that in place, I could see the issue was "too many open files". Checking <a href="https://mastodon.bsd.cafe/tags/ulimit" class="mention hashtag" rel="nofollow noopener" target="_blank">#ulimit</a> -n gave me 1024. Seriously? 🤯 On my <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> machine, as a regular user, it's 226755. Ok, bumped that up to 8192 and then the stress test ran through without issues.On a side note, this also made creating new timers (using <a href="https://mastodon.bsd.cafe/tags/timerfd" class="mention hashtag" rel="nofollow noopener" target="_blank">#timerfd</a> on Linux) fail, which ultimately made swad crash. I have to redesign my timer interface so that creating a timer may explicitly fail and I can react on that, aborting whatever would need that timer.Anyways, the same test gave somewhat acceptable results: throughput of roughly 3000 req/s, response times around 500ms. Not great, but okayish, and not directly comparable because this test ran in a <a href="https://mastodon.bsd.cafe/tags/bhyve" class="mention hashtag" rel="nofollow noopener" target="_blank">#bhyve</a> vm and the requests had to pass the virtual networking.One major issue is still the <a href="https://mastodon.bsd.cafe/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#RAM</a> consumption. The test left swad with a resident set of > 540 MiB. I have no idea what to do about that. 😞 The code makes heavy use of "allocated objects" (every connection object with metadata and buffers, every event handler registered, every timer, and so on), so, uses the <a href="https://mastodon.bsd.cafe/tags/heap" class="mention hashtag" rel="nofollow noopener" target="_blank">#heap</a> a lot, but according to <a href="https://mastodon.bsd.cafe/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a>, correctly frees everything. Still the resident set just keeps growing. I guess it's the classic <a href="https://mastodon.bsd.cafe/tags/fragmentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#fragmentation</a> issue...

Felix Palmen :freebsd: :c64:Hm, is <a href="https://mastodon.bsd.cafe/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a>'s <a href="https://mastodon.bsd.cafe/tags/helgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#helgrind</a> useless for code using <a href="https://mastodon.bsd.cafe/tags/atomic" class="mention hashtag" rel="nofollow noopener" target="_blank">#atomic</a> operations? Example, it complains about this:==9505== Possible data race during read of size 4 at 0xADD57F4 by thread #14 ==9505== Locks held: none ==9505== at 0x23D0F1: PSC_ThreadPool_cancel (threadpool.c:761) [....] ==9505== This conflicts with a previous write of size 4 by thread #6 ==9505== Locks held: none ==9505== at 0x23CDDE: worker (threadpool.c:373)so, here's threadpool.c:761: if ((pthrno = atomic_load_explicit( &job->pthrno, memory_order_consume)) >= 0)and here's threadpool.c:373: atomic_store_explicit(&currentJob->pthrno, -1, memory_order_release);Ok, I *think* this should be fine? Do I miss something?(screenshots for readability ...)<a href="https://mastodon.bsd.cafe/tags/c" class="mention hashtag" rel="nofollow noopener" target="_blank">#c</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a> <a href="https://mastodon.bsd.cafe/tags/c11" class="mention hashtag" rel="nofollow noopener" target="_blank">#c11</a> <a href="https://mastodon.bsd.cafe/tags/atomics" class="mention hashtag" rel="nofollow noopener" target="_blank">#atomics</a>

SourcewareSourceware Survey 2025 ResultsIn the end we got 103 (!) responses with a nice mix of developers, users and maintainers from various hosted projects.<a href="https://sourceware.org/survey-2025" rel="nofollow noopener" translate="no" target="_blank">https://sourceware.org/survey-2025</a><a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a> <a href="https://fosstodon.org/tags/cygwin" class="mention hashtag" rel="nofollow noopener" target="_blank">#cygwin</a> <a href="https://fosstodon.org/tags/dwarfstd" class="mention hashtag" rel="nofollow noopener" target="_blank">#dwarfstd</a> <a href="https://fosstodon.org/tags/elfutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#elfutils</a> <a href="https://fosstodon.org/tags/gcc" class="mention hashtag" rel="nofollow noopener" target="_blank">#gcc</a> <a href="https://fosstodon.org/tags/gdb" class="mention hashtag" rel="nofollow noopener" target="_blank">#gdb</a> <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://fosstodon.org/tags/libabigail" class="mention hashtag" rel="nofollow noopener" target="_blank">#libabigail</a> <a href="https://fosstodon.org/tags/newlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#newlib</a> <a href="https://fosstodon.org/tags/systemTap" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemTap</a> <a href="https://fosstodon.org/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> <a href="https://fosstodon.org/tags/bzip2" class="mention hashtag" rel="nofollow noopener" target="_blank">#bzip2</a> <a href="https://fosstodon.org/tags/libffi" class="mention hashtag" rel="nofollow noopener" target="_blank">#libffi</a> <a href="https://fosstodon.org/tags/dwz" class="mention hashtag" rel="nofollow noopener" target="_blank">#dwz</a> <a href="https://fosstodon.org/tags/debugedit" class="mention hashtag" rel="nofollow noopener" target="_blank">#debugedit</a> <a href="https://fosstodon.org/tags/gnupoke" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnupoke</a> <a href="https://fosstodon.org/tags/bunsen" class="mention hashtag" rel="nofollow noopener" target="_blank">#bunsen</a> <a href="https://fosstodon.org/tags/lvm2" class="mention hashtag" rel="nofollow noopener" target="_blank">#lvm2</a> <a href="https://fosstodon.org/tags/annobin" class="mention hashtag" rel="nofollow noopener" target="_blank">#annobin</a> <a href="https://fosstodon.org/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnu</a>-gabi <a href="https://fosstodon.org/tags/cgen" class="mention hashtag" rel="nofollow noopener" target="_blank">#cgen</a> <a href="https://fosstodon.org/tags/kawa" class="mention hashtag" rel="nofollow noopener" target="_blank">#kawa</a> <a href="https://fosstodon.org/tags/insight" class="mention hashtag" rel="nofollow noopener" target="_blank">#insight</a> <a href="https://fosstodon.org/tags/pacme" class="mention hashtag" rel="nofollow noopener" target="_blank">#pacme</a>

mjwPlease help test <a href="https://mastodon.nl/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> 3.25.0-RC1<a href="https://sourceforge.net/p/valgrind/mailman/message/59174627/" rel="nofollow noopener" translate="no" target="_blank">https://sourceforge.net/p/valgrind/mailman/message/59174627/</a>Initial RISCV64/Linux support. Valgrind gdbserver supports 'x' packets. Bug fixes for Illumos. --track-fds=yes treats inherited file descriptors like stdin/out/err (0,1,2). There is --modify-fds=high. s390x support for new instructions (BPP, BPRP and NIAI). New linux syscalls supported (landlock*, open_tree, move_mount, fsopen, fsconfig, fsmount, fspick, userfaultfd). The Linux Test Project (ltp) is integrated in the testsuite.

Felix Palmen :freebsd: :c64:Nice, <a href="https://mastodon.bsd.cafe/tags/threadpool" class="mention hashtag" rel="nofollow noopener" target="_blank">#threadpool</a> overhaul done. Removed two locks (<a href="https://mastodon.bsd.cafe/tags/mutex" class="mention hashtag" rel="nofollow noopener" target="_blank">#mutex</a>) and two condition variables, replaced by a single lock and a single <a href="https://mastodon.bsd.cafe/tags/semaphore" class="mention hashtag" rel="nofollow noopener" target="_blank">#semaphore</a>. 😎 Simplifies the overall structure a lot, and it's probably safe to assume slightly better performance in contended situations as well. And so far, <a href="https://mastodon.bsd.cafe/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a>'s helgrind tool doesn't find anything to complain about. 🙃Looking at the screenshot, I should probably make <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#swad</a> default to *two* threads per CPU and expose the setting in the configuration file. When some thread jobs are expected to block, having more threads than CPUs is probably better.<a href="https://github.com/Zirias/poser/commit/995c27352615a65723fbd1833b2d36781cbeff4d" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/poser/commit/995c27352615a65723fbd1833b2d36781cbeff4d</a>

arielsFriend <a href="https://dice.camp/@Computer" class="u-url mention" rel="nofollow noopener" target="_blank">@Computer</a> I streamlined multiple levels of security by trouble shooting them. Our new security posture eliminates treacherous "defense in depth" wasted and disloyal effort. (This repeats earlier work that fixed <a href="https://hachyderm.io/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> runs on <a href="https://hachyderm.io/tags/openssl" class="mention hashtag" rel="nofollow noopener" target="_blank">#openssl</a>, and of course recent similar improvements carried out by <a href="https://hachyderm.io/tags/doge_doofus" class="mention hashtag" rel="nofollow noopener" target="_blank">#doge_doofus</a>)

mjwMonitor <a href="https://mastodon.nl/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a> compile time by Andrew MacLeod.<a href="https://developers.redhat.com/articles/2025/01/22/monitor-gcc-compile-time" rel="nofollow noopener" translate="no" target="_blank">https://developers.redhat.com/articles/2025/01/22/monitor-gcc-compile-time</a>Explaining how to use <a href="https://mastodon.nl/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> callgrind for profiling and analyzing your program runtime behavior.

mjwDebuginfod project update 2024 by Aaron Merey<a href="https://developers.redhat.com/articles/2025/01/14/debuginfod-project-update-2024" rel="nofollow noopener" translate="no" target="_blank">https://developers.redhat.com/articles/2025/01/14/debuginfod-project-update-2024</a>- Metrics and scale of debuginfod servers <a href="https://mastodon.nl/tags/prometheus" class="mention hashtag" rel="nofollow noopener" target="_blank">#prometheus</a> - New tools and features in debuginfod <a href="https://mastodon.nl/tags/elfutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#elfutils</a> - IMA verification support - Addressing kernel VDSO extraction bottlenecks <a href="https://fosstodon.org/@osandov" class="u-url mention" rel="nofollow noopener" target="_blank">@osandov</a> - Lazy debug info downloading in <a href="https://mastodon.nl/tags/Valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#Valgrind</a> and <a href="https://mastodon.nl/tags/GDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDB</a>

Mai :v_trans:Built my <a href="https://codearq.net/mai-lapyst/sexpr-zig" rel="nofollow noopener" target="_blank">first lisp</a> (after already having started writing two compilers xD) in <a href="https://soc.saiyajin.space/tags/zig" class="mention hashtag" rel="nofollow noopener" target="_blank">#zig</a>! Mainly to test out the language, but it was much fun anyway.It also got a few ideas for my own language for a few functional programming things :DI enoyied the most the memory checking zig does, be it leaks, use-after-free or double-free, which makes this project the most easy to be memory-safe out of all my native (c-like) projects whithout multiple days using <a href="https://soc.saiyajin.space/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> xD<a href="https://soc.saiyajin.space/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://soc.saiyajin.space/tags/oss" class="mention hashtag" rel="nofollow noopener" target="_blank">#oss</a> <a href="https://soc.saiyajin.space/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://soc.saiyajin.space/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://soc.saiyajin.space/tags/langdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#langdev</a> <a href="https://soc.saiyajin.space/tags/lisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#lisp</a> <a href="https://soc.saiyajin.space/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a> <a href="https://soc.saiyajin.space/tags/c" class="mention hashtag" rel="nofollow noopener" target="_blank">#c</a> <a href="https://soc.saiyajin.space/tags/c" class="mention hashtag" rel="nofollow noopener" target="_blank">#c</a>++ <a href="https://soc.saiyajin.space/tags/zig" class="mention hashtag" rel="nofollow noopener" target="_blank">#zig</a> <a href="https://soc.saiyajin.space/tags/functionalprograming" class="mention hashtag" rel="nofollow noopener" target="_blank">#functionalprograming</a> <a href="https://soc.saiyajin.space/tags/compilerdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#compilerdev</a>

mjw<a href="https://mastodon.nl/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> 3.24.0 released!<a href="https://valgrind.org/docs/manual/dist.news.html" rel="nofollow noopener" translate="no" target="_blank">https://valgrind.org/docs/manual/dist.news.html</a>Sourceware download: <a href="https://valgrind.org/downloads/current.html#current" rel="nofollow noopener" translate="no" target="_blank">https://valgrind.org/downloads/current.html#current</a>

mjwSome of the tricks that were needed to support x86-64-v3 in <a href="https://mastodon.nl/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> memcheck:<a href="https://developers.redhat.com/articles/2024/10/24/preparing-valgrind-memcheck-x86-64-v3" rel="nofollow noopener" translate="no" target="_blank">https://developers.redhat.com/articles/2024/10/24/preparing-valgrind-memcheck-x86-64-v3</a>

benwebbJust used valgrind for the first time in a while. And it's great! But I wonder if there are any alternatives in use today? Address Sanitizer?<a href="https://mstdn.social/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> <a href="https://mstdn.social/tags/c" class="mention hashtag" rel="nofollow noopener" target="_blank">#c</a> <a href="https://mstdn.social/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#clang</a> <a href="https://mstdn.social/tags/debuggers" class="mention hashtag" rel="nofollow noopener" target="_blank">#debuggers</a>

Felix Palmen :freebsd: :c64:<a href="https://mastodon.bsd.cafe/@matuzalem" class="u-url mention" rel="nofollow noopener" target="_blank">@matuzalem</a> here's a release to test 😉 I'm pretty sure it won't crash, but can't guarantee. It's been examined a lot, also with <a href="https://mastodon.bsd.cafe/tags/lldb" class="mention hashtag" rel="nofollow noopener" target="_blank">#lldb</a> and <a href="https://mastodon.bsd.cafe/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a>, but doesn't have any automated tests so far. I'm still undecided about investing the time and effort to change that, would need to pick a library/framework first (C doesn't offer any testing capabilities in the language) and then, while a few modules like the unicode string functions are perfectly unit-testable, the whole project is a large "event processor" (like any GUI application) and depends on these external events, so a *lot* of tedious mocking would be required for better test coverage ...edit: btw, fixed a weird bug before releasing this, it was possible to enter a state where processing X11 events stopped (requesting to minimize with the WM ignoring the request). Not a crash, but a bug 😅

André Machado :debian:Valgrind is an open-source programming tool used primarily for memory debugging, memory leak detection, and profiling. Developed by Julian Seward and first released in 2002, Valgrind is a suite of simulation-based debugging and profiling tools that help developers improve the performance and correctness of their programs. It supports various programming languages.More about this introduction to Valgrind, check: <a href="https://machaddr.substack.com/p/introduction-to-valgrind" rel="nofollow noopener" target="_blank">https://machaddr.substack.com/p/introduction-to-valgrind</a><a href="https://mastodon.sdf.org/tags/Valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#Valgrind</a> <a href="https://mastodon.sdf.org/tags/overflow" class="mention hashtag" rel="nofollow noopener" target="_blank">#overflow</a> <a href="https://mastodon.sdf.org/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mastodon.sdf.org/tags/language" class="mention hashtag" rel="nofollow noopener" target="_blank">#language</a> <a href="https://mastodon.sdf.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

you╭👺+300╭🐈x5╭⁂+3╭(Ⓐ+aSo, having hacked together some <a href="https://mastodon.social/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> bindings for <a href="https://mastodon.social/tags/suil" class="mention hashtag" rel="nofollow noopener" target="_blank">#suil</a> that compile, apparently now I gotta <a href="https://mastodon.social/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> the hell out of that stuff.Shout out to <a href="https://social.jvns.ca/@b0rk" class="u-url mention" rel="nofollow noopener" target="_blank">@b0rk</a> for <a href="https://jvns.ca/blog/2017/12/23/segfault-debugging/" rel="nofollow noopener" translate="no" target="_blank">https://jvns.ca/blog/2017/12/23/segfault-debugging/</a> - I would've been completely lost without this guide! Instead I will now proceed to load me some <a href="https://mastodon.social/tags/lv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#lv2</a> plugins and kick me some tunesAt least I didn't have to package suil myself, it's on <a href="https://mastodon.social/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener" target="_blank">#nixpkgs</a>! yay nixpkgs

mjwThe <a href="https://mastodon.nl/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> project closed 110 bugs these last 6 months, but there were also 85 new bugs opened. So the good news is that we are closing bugs faster than they are filed now and we dropped under 1000 open bugs. The bad news is that there are still 975 open bugs. Which is still a slightly intimidating number of bugs.<a href="https://sourceforge.net/p/valgrind/mailman/message/58787822/" rel="nofollow noopener" translate="no" target="_blank">https://sourceforge.net/p/valgrind/mailman/message/58787822/</a>

Sourceware<a href="https://fosstodon.org/tags/Sourceware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sourceware</a> @ <a href="https://fosstodon.org/tags/Fosdem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fosdem</a> 2024Various Sourceware projects will give presentations at <a href="https://fosstodon.org/@fosdem" class="u-url mention" rel="nofollow noopener" target="_blank">@fosdem</a> next weekend, Feb 3 and 4, in Brussels.Guinevere, Dodji, Jose, David and Thomas organized some great devroom talks:<a href="https://inbox.sourceware.org/20240128203842.GE15739@gnu.wildebeest.org/" rel="nofollow noopener" translate="no" target="_blank">https://inbox.sourceware.org/20240128203842.GE15739@gnu.wildebeest.org/</a>Various Sourceware volunteers, overseers, PLC members and <a href="https://social.sfconservancy.org/users/conservancy" class="u-url mention" rel="nofollow noopener" target="_blank">@conservancy</a> staff will also be around.<a href="https://fosstodon.org/tags/gdb" class="mention hashtag" rel="nofollow noopener" target="_blank">#gdb</a> <a href="https://fosstodon.org/tags/libabigail" class="mention hashtag" rel="nofollow noopener" target="_blank">#libabigail</a> <a href="https://fosstodon.org/tags/systemtap" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemtap</a> <a href="https://fosstodon.org/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> <a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a> <a href="https://fosstodon.org/tags/elfutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#elfutils</a> <a href="https://fosstodon.org/tags/gcc" class="mention hashtag" rel="nofollow noopener" target="_blank">#gcc</a> <a href="https://fosstodon.org/tags/newlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#newlib</a> <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://fosstodon.org/tags/gnupoke" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnupoke</a>

Howard Chu @ Symas<a href="https://mas.to/@zekjur" class="u-url mention" rel="nofollow noopener" target="_blank">@zekjur</a> sounds cool. It'd be a good addition to <a href="https://mastodon.social/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a>. It also reminds me of a modification of qemu (called temu) that did execution tracing, done at UC Berkeley a long time ago.

mjwA thousand bugs. That is how many open <a href="https://mastodon.nl/tags/Valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#Valgrind</a> bugs there are at the moment. Wondering what the best method is to deal with this.<a href="https://sourceforge.net/p/valgrind/mailman/message/51809032/" rel="nofollow noopener" translate="no" target="_blank">https://sourceforge.net/p/valgrind/mailman/message/51809032/</a>

Jim RamsayNo! As usual, the reviews and IRC chats with <a href="https://mastodon.social/@andriyngvason" class="u-url mention" rel="nofollow noopener" target="_blank">@andriyngvason</a> were extremely kind and valuable.First of all, wayvncctl needed a better human-friendly pretty-printer for the json responses. Sure!More importantly, we were using libjansson for the json library which uses a refcount system for memory management. <a href="https://fosstodon.org/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> pointed out a number of mistakes I made on both the server and the client that required more refactoring.Finally, it was ready: <a href="https://github.com/any1/wayvnc/pull/171" rel="nofollow noopener" translate="no" target="_blank">https://github.com/any1/wayvnc/pull/171</a>

Recent searches

Search options

Administered by:

Server stats:

#valgrind