[Bug 273956] KERN_PROC_VMMAP does not read all mapped files

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 20 Sep 2023 14:51:04 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956

--- Comment #3 from Paul Floyd <pjfloyd@wanadoo.fr> ---
Hi Ed

Which versions of FreeBSD and Valgrind are you using?

I was running my dev buuild of Valgrind under gdb when I ran procstat.

The easiest thing is to use a dummy exe that just does a big sleep() and then
run valgrind normally.

Alternatively, to run in gdb, set the folowing env vars:

(1) Set VALGRIND_LAUNCHER to point to the valgrind executable.  Eg:

      export VALGRIND_LAUNCHER=/usr/local/bin/valgrind

    or for an uninstalled version in a source directory $DIR:

      export VALGRIND_LAUNCHER=$DIR/coregrind/valgrind
      export VALGRIND_LIB=$DIR/.in_place

    VALGRIND_LIB is where the default.supp and vgpreload_ libraries
    are found

You should run something like

gdb --args /path/to/memcheck-amd64-freebsd --tool=memcheck `which false`

There's no main, if you want to start at the beginning put a break on
valgrind_main.

For this report I put a breakpoint on 'parse_procselfmaps' which is reached
fairly early on.

If you do debug much futher than that you should let Valgrind handle
exceptions:

 handle SIGILL SIGSEGV nostop noprint  

lldb should work as well but I mainly use gdb because Valgrind doesn't yet have
an integrated lldb-server

Ignoring signals with lldb:
pro hand -p true -s false -n false SIGILL SIGSEGV

-- 
You are receiving this mail because:
You are the assignee for the bug.