From nobody Thu Oct 16 17:15:42 2025 X-Original-To: dev-commits-doc-all@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cnZNG4g53z6Cpr4 for ; Thu, 16 Oct 2025 17:15:42 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R12" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cnZNG3tvwz3rk6; Thu, 16 Oct 2025 17:15:42 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1760634942; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=n61swTFUIEqqPa+UFyaOxs0t5+0u1wkPfQl04lSkHN8=; b=hR9Xvu8wvGXBwbvgX+kX3cUd9PWXmzUsR/ZSb49wc7ujgIhcNNZ84voY9XScAjgy1Lifti tkdnhiJBbE9AvLLpVqDv+q+wTrv6tkioVJN7UjFXYHRvFIjt4Pg1m0jcOikUrqqiFv9Bpu ZgfCJAYB+yA+FAwfNZpNh68Uxza3sud4a9NZGBMcIMV7hHLPrbLvg8BdStV7baKsJHqCap 8PCFnazSAQ4QfSAB5cEsxEI1Rcn4qj8gyU+8QedSX8IkRaEukC0zHZ3Ow6Skp5hb1kdxGu 2YH9oPr9lvbafRT59baqIcDPYScCyEXMhAFPuh9xoySq3teJTY3xT9o4UZJtLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1760634942; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=n61swTFUIEqqPa+UFyaOxs0t5+0u1wkPfQl04lSkHN8=; b=Rq6cD8ZrP/qt2EPJ36IhGG/TnILZBJM5foXAHgUo+Sq2kAR7WNm+jY6pJF67LmXbnsRywe dV3WQXfM7korQU3G8WoVJO5LfiQqDWg5zuSyc4Z5HrJXF9q4pAXBv0hBiZbUTlpVEyhBvU E6K9LxqxEHGsnfbfkLA4s6ES+81+Vu74264+cqUyTEmYZh8vCgucUSO7EKHv0fiylG5R0x w7oo85Rd0jzl4JonBQRzF9p7+PjoNVMOJxOCOo2hQ3Yj79pfzD6W84QuOdFZYx5aox5yp1 ZG4pK6ZVRsv8xu4Cjq8K+YUofYgFbL1qKhNXAaFVY7vZxUbK9lWcr4kmg44iMA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1760634942; a=rsa-sha256; cv=none; b=H0SS4zxbcZnqg01/aPYf6P9kixOWHHYbH3tAttdQXT4AqWNmw8VwgTrvEnK39Da9QbshhX ljrS7OPoVP+qR7W8+mm8JE4OvCoiJpNfPv8GFENhsHhBRDquZROQi2khsT97tAqqkbCE85 OtEMD7kYAIak2TfuxSYq/N/x+HBaWCqPcalxq8j7mHlCIA6SCVhGjt380RiqA6Y/+fdwbo xTs1iff6vnL2eLpld2RRY7ldwQABIssCvoBSyIBhRy1ZfPu5mpmp8bB3uWRjjzGOSzjwMR lz798ALsDFyV5snOxfChT5v9zAfRlmGsaMub5cvKgF7jMXx+MBvZwFyJg1CZmw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4cnZNG2zR4z2l9; Thu, 16 Oct 2025 17:15:42 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.18.1/8.18.1) with ESMTP id 59GHFg9h094044; Thu, 16 Oct 2025 17:15:42 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.18.1/8.18.1/Submit) id 59GHFg8h094041; Thu, 16 Oct 2025 17:15:42 GMT (envelope-from git) Date: Thu, 16 Oct 2025 17:15:42 GMT Message-Id: <202510161715.59GHFg8h094041@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Maxim Konovalov Subject: git: 290d919377 - main - status/valgrind: spell List-Id: Commit messages for all branches of the doc repository List-Archive: https://lists.freebsd.org/archives/dev-commits-doc-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: dev-commits-doc-all@freebsd.org Sender: owner-dev-commits-doc-all@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: maxim X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 290d919377831f3685ffd5766e91d2d7fb36d996 Auto-Submitted: auto-generated The branch main has been updated by maxim: URL: https://cgit.FreeBSD.org/doc/commit/?id=290d919377831f3685ffd5766e91d2d7fb36d996 commit 290d919377831f3685ffd5766e91d2d7fb36d996 Author: Maxim Konovalov AuthorDate: 2025-10-16 17:15:11 +0000 Commit: Maxim Konovalov CommitDate: 2025-10-16 17:15:11 +0000 status/valgrind: spell --- website/content/en/status/report-2025-07-2025-09/valgrind.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/content/en/status/report-2025-07-2025-09/valgrind.adoc b/website/content/en/status/report-2025-07-2025-09/valgrind.adoc index d836878b21..ea8fb619fc 100644 --- a/website/content/en/status/report-2025-07-2025-09/valgrind.adoc +++ b/website/content/en/status/report-2025-07-2025-09/valgrind.adoc @@ -7,9 +7,9 @@ link:https://github.com/paulfloyd/freebsdarm64_valgrind[arm64 port] URL: link:ht Contact: Paul Floyd -I have not submitted any reports for over a year. On the whole that is good news as it means that there have not been any major issues. Back then I said that aarch64 support was about to land and indeed it dit in mid April 2024. +I have not submitted any reports for over a year. On the whole that is good news as it means that there have not been any major issues. Back then I said that aarch64 support was about to land and indeed it did in mid April 2024. -I added a nice little script for use with Valgrind called `vgscript`. This works in a similar manner to `pstack` (or `bstack` on FreeBSD) in that you give it a PID and it will generate a stack trace for that process. If you use `bstack` with a Valgrind process you will see the Valgrind call stack which is probabably of no use to you. If you run `vgstack` with a Valgrind PID it will print the call stack of the test exe running under Valgrind. +I added a nice little script for use with Valgrind called `vgscript`. This works in a similar manner to `pstack` (or `bstack` on FreeBSD) in that you give it a PID and it will generate a stack trace for that process. If you use `bstack` with a Valgrind process you will see the Valgrind call stack which is probably of no use to you. If you run `vgstack` with a Valgrind PID it will print the call stack of the test exe running under Valgrind. If you use Valgrind regularly could you take a look and answer the survey that I posted on the forums (if you have not done so already). Here is the link:https://forums.freebsd.org/threads/valgrind-feature-poll.98707/#post-716085[link]. @@ -18,7 +18,7 @@ Valgrind 3.26 is due out at the end of October 2025 and package:devel/valgrind[] package:devel/valgrind-devel[] will get one (or maybe more) updates as I fix issues with FreeBSD 15.0. -The oustanding issues that I have on FreeBSD 15.0 are +The outstanding issues that I have on FreeBSD 15.0 are * aarch64: there is a problem when using Valgrind with gdb/vgdb. Hitting ctrl-c to interrupt the process running under Valgrind does not work and Valgrind crashes with an assert. * aarch64: a known old issue that was infrequent regarding initialisation of thread memory now seems to occur much more often. * amd64: maybe similar to the first issue with gdb/vgdb and interrupting a process, but this time I'm seeing `select` return an 'impossible' value.