https://bugs.kde.org/show_bug.cgi?id=464476
Paul Floyd <pjfl...@wanadoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Paul Floyd <pjfl...@wanadoo.fr> ---
Running firefox under memcheck to close this item !
commit 5d387642049bf366d913f572269f8bf16627ac10
Author: Paul Floyd <pjfl...@wanadoo.fr>
Date: Sat Jan 21 17:55:09 2023 +0100
Bug 464476 - Firefox fails to start under Valgrind
On FreeBSD, Firefox uses the kern.proc.pathname.PID sysctl
to get the binary path (where PID can be the actual pid
or -1). The user path is /usr/local/bin/firefox which is
a symlink to /usr/local/lib/firefox/firefox.
This was failing because we were not handling this MIB.
That meant that the sysctl returned the path for the
binary of the running tool (e.g.,
/home/paulf/scratch/valgrind/memcheck/memcheck-amd64-freebsd).
Firefox looks for files in the same directory.
Since it was the wrong directory it failed to find them and
exited.
I also noticed a lot of _umtx_op errors. On analysis they
are spurious. The wake ops take an "obj" argument, a pointer
to a variable. They only use the address as a key for
lookups and don't read the contents.
--
You are receiving this mail because:
You are watching all bug changes.
