[valgrind] [Bug 464476] Firefox fails to start under Valgrind

2023-01-21 Thread Paul Floyd
|--- |FIXED --- Comment #4 from Paul Floyd --- Running firefox under memcheck to close this item ! commit 5d387642049bf366d913f572269f8bf16627ac10 Author: Paul Floyd Date: Sat Jan 21 17:55:09 2023 +0100 Bug 464476 - Firefox fails to start under Valgrind On FreeBSD, Firefox uses

[valgrind] [Bug 464476] Firefox fails to start under Valgrind

2023-01-19 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=464476 --- Comment #3 from Paul Floyd --- Almost there. I use VG_(find_executable)(VG_(args_the_exename)) then check if it is a link and if so call VG_(readlink)(exe_name, out, VKI_PATH_MAX); But readlink doesn't resolve relative paths to absolute paths.

[valgrind] [Bug 464476] Firefox fails to start under Valgrind

2023-01-19 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=464476 --- Comment #2 from Paul Floyd --- A bit trickier than I thought since firefox is a symlink and I need to first resolve the symlink. We don't have a VG_(lstat) as far as I can see. -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 464476] Firefox fails to start under Valgrind

2023-01-18 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=464476 --- Comment #1 from Paul Floyd --- There problem is with sysctl kern.proc.pathname.PID This is used to determine the full path of firefox, but when it runs under valgrind it returns the path to valgrind instead. firefox then looks in the valgrind

[valgrind] [Bug 464476] Firefox fails to start under Valgrind

2023-01-18 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=464476 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this