kaiwan/procmap

Visualization of the COMPLETE MEMORY MAP of any given process

procmap's Issues

ps, smem run at end doesn't work when PID is that of a (worker/child) thread

Check for type - process or thread - and accordingly branch off

Fedora 36: suitable build env for kernel modules missing error, but kernel headers are installed

I have kernel headers installed on Fedora 36:

[16:42:13] others/procmap::master ✔ dnf info kernel-headers
Last metadata expiration check: 0:42:02 ago on Fri 11 Nov 2022 04:00:23 PM CET.
Installed Packages
Name         : kernel-headers
Version      : 6.0.5
Release      : 200.fc36
Architecture : x86_64
Size         : 5.8 M
Source       : kernel-headers-6.0.5-200.fc36.src.rpm
Repository   : @System
From repo    : updates
Summary      : Header files for the Linux kernel for use by glibc
URL          : http://www.kernel.org/
License      : GPLv2
Description  : Kernel-headers includes the C header files that specify the interface
             : between the Linux kernel and userspace libraries and programs.  The
             : header files define structures and constants that are needed for
             : building most standard programs and are also needed for rebuilding the
             : glibc package.

Yet I get the following error message when running procmap:

[16:08:06] others/procmap::master ✔ ./procmap --pid=1
[i] will display memory map for process PID=1
Place your finger on the fingerprint reader
[i] kernel: building the procmap LKM now...
 FatalError :: procmap: suitable build env for kernel modules is missing! Pl install the Linux kernel headers (via the appropriate package). If you cannot install a 'kernel headers' package (perhaps you're running a custom built kernel), then you will need to cross-compile the procmap kernel module on your host and copy it across to the target device. Pl see this project's README.md file for details (section 'IMPORTANT: Running procmap on systems other than x86_64').
  Stack Call-trace:
   [frame #1] /home/mk/Projects/others/procmap/err_common.sh:cli_handle_error:116        <-- top of stack
   [frame #2] /home/mk/Projects/others/procmap/err_common.sh:FatalError:183
   [frame #3] /home/mk/Projects/others/procmap/lib_procmap.sh:build_lkm:214
   [frame #4] /home/mk/Projects/others/procmap/lib_procmap.sh:init_kernel_lkm_get_details:317
   [frame #5] ./procmap:main:0
/home/mk/Projects/others/procmap/lib_procmap.sh: line 526: /tmp/procmap/arch_dtl: No such file or directory
 FatalError :: procmap: could not source /tmp/procmap/arch_dtl , aborting...
  Stack Call-trace:
   [frame #1] /home/mk/Projects/others/procmap/err_common.sh:cli_handle_error:116        <-- top of stack
   [frame #2] /home/mk/Projects/others/procmap/err_common.sh:FatalError:527
   [frame #3] /home/mk/Projects/others/procmap/lib_procmap.sh:get_machine_set_arch_config:318
   [frame #4] ./procmap:main:0
./procmap: line 323: /tmp/procmap/arch_dtl: No such file or directory
/home/mk/Projects/others/procmap/do_kernelseg.sh: line 12: /tmp/procmap/arch_dtl: No such file or directory
procmap: fatal: could not source /tmp/procmap/arch_dtl , aborting...

Is this expected?

uname -a
Linux carbon-x1 6.0.5-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Oct 26 15:55:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

On FC38 heap shows in wrong location

[heap] showing right at the top of userspace!??

...
+------------------      U S E R   V A S    end uva  ------------------+ 00007fffffffffff
|              [heap]  [ 132 KB,rw-,p,0x0]                             |
|                                                                      |
+----------------------------------------------------------------------+ 0000000000820000
|<... Sparse Region ...> [   4.10 MB,---,-,0x0]                        |
|                                                                      |
|                                                                      |
+----------------------------------------------------------------------+ 00007fffffffffff
|<... Sparse Region ...> [  12.47 GB,---,-,0x0]                        |
|                                                                      |
...

Likely due to proc showing va's with leading zeroes!?