Date: Fri, 20 Jan 2023 10:09:34 +0100 From: "Floyd, Paul" <paulf2718@gmail.com> To: "gecko@freebsd.org" <gecko@FreeBSD.org> Subject: www/firefox and valgrind Message-ID: <b55a0a4e-5fa1-84eb-3f8d-d55a098fff4e@gmail.com>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------MgGnnhhTbHf3KMtilA3IXkfb Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Just a quick heads up for an upcoming FreeBSD Firefox related item. I maintain Valgrind and I’m getting close to fixing an issue that prevented FF from running under Valgrind (https://bugs.kde.org/show_bug.cgi?id=464476) FF has a bit of a special status in the Valgrind world as the two main contributors work at Mozilla. I guess I’ll push a fix for this upstream this weekend. I don’t know exactly when I’m going to bump up the ports versions. “devel/valgrind” will likely change in April when Valgrind 3.21 gets released. I’m also thinking of making an intermediate release of “devel/valgrind-devel” in the next few weeks. In the meantime I am seeing quite a lot of errors: - _umtx_op syscall argument errors (probably a false positive and needs fixing in Valgrind) - mismatched malloc/new/free/deletes (possibly class-specific operator noew?) - some unrecognized instructions in wasm (surprisingly didn't cause SIGILL crashes) - uninitiated bytes in sendmsg (generally throws up a lot of errors due to holes/padding in structures). I suspect that points 2 and 3 are covered by https://firefox-source-docs.mozilla.org/contributing/debugging/debugging_firefox_with_valgrind.html which I hadn't seen and read before doing my first tests. I may be opening some buzgilla items against firefox in the coming weeks. I'll also give FF/Linux a go to see how noisy that is. A+ Paul --------------MgGnnhhTbHf3KMtilA3IXkfb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"> Hi <div><br> </div> <div>Just a quick heads up for an upcoming FreeBSD Firefox related item.</div> <div><br> </div> <div>I maintain Valgrind and I’m getting close to fixing an issue that prevented FF from running under Valgrind</div> <div><br> </div> <div>(<a href="https://bugs.kde.org/show_bug.cgi?id=464476" moz-do-not-send="true" class="moz-txt-link-freetext">https://bugs.kde.org/show_bug.cgi?id=464476</a>)</div>; <div><br> </div> <div>FF has a bit of a special status in the Valgrind world as the two main contributors work at Mozilla.</div> <div><br> </div> <div>I guess I’ll push a fix for this upstream this weekend. I don’t know exactly when I’m going to bump up the ports versions. “devel/valgrind” will likely change in April when Valgrind 3.21 gets released. I’m also thinking of making an intermediate release of “devel/valgrind-devel” in the next few weeks.</div> <div><br> </div> <div>In the meantime I am seeing quite a lot of errors:<br> </div> <div><br> </div> <div>- _umtx_op syscall argument errors (probably a false positive and needs fixing in Valgrind)<br> </div> <div>- mismatched malloc/new/free/deletes (possibly class-specific operator noew?)</div> <div>- some unrecognized instructions in wasm (surprisingly didn't cause SIGILL crashes)</div> <div>- uninitiated bytes in sendmsg (generally throws up a lot of errors due to holes/padding in structures).</div> <div><br> </div> <div>I suspect that points 2 and 3 are covered by</div> <div><a class="moz-txt-link-freetext" href="https://firefox-source-docs.mozilla.org/contributing/debugging/debugging_firefox_with_valgrind.html">https://firefox-source-docs.mozilla.org/contributing/debugging/debugging_firefox_with_valgrind.html</a></div>; <div>which I hadn't seen and read before doing my first tests.<br> </div> <div><br> </div> <div>I may be opening some buzgilla items against firefox in the coming weeks.</div> <div><br> </div> <div>I'll also give FF/Linux a go to see how noisy that is.<br> </div> <div><br> </div> <div>A+</div> <div>Paul</div> <div><br> </div> </body> </html> --------------MgGnnhhTbHf3KMtilA3IXkfb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b55a0a4e-5fa1-84eb-3f8d-d55a098fff4e>