#proc #maps #memory #virtual #helper

proc-maps

Helper crate for getting virtual memory maps from processes

7 releases

Uses old Rust 2015

0.1.8 Apr 4, 2021
0.1.7 Mar 21, 2021
0.1.6 Jul 14, 2019
0.1.5 Nov 20, 2018
0.1.4 Aug 31, 2018
Download history 91/week @ 2020-12-25 138/week @ 2021-01-01 239/week @ 2021-01-08 737/week @ 2021-01-15 194/week @ 2021-01-22 156/week @ 2021-01-29 650/week @ 2021-02-05 520/week @ 2021-02-12 629/week @ 2021-02-19 431/week @ 2021-02-26 634/week @ 2021-03-05 824/week @ 2021-03-12 1405/week @ 2021-03-19 2354/week @ 2021-03-26 9017/week @ 2021-04-02 4675/week @ 2021-04-09

3,056 downloads per month
Used in 6 crates (4 directly)

MIT license

57KB
1.5K SLoC

proc-maps

Build Status Windows Build status crates.io docs.rs

This crate supports reading virtual memory maps from another process - and supports Linux OSX and Windows operating systems.

Example:

use proc_maps::{get_process_maps, MapRange};

let maps = get_process_maps(pid)?;
for map in maps {
    println!("Filename {} Address {} Size {}", map.filename(), map.start(), map.size());
}

This code was originally developed by Julia Evans as part of the rbspy project: https://github.com/rbspy/rbspy.

Release under the MIT License.


lib.rs:

Get virtual memory maps from another process

This crate provides a function—get_process_maps that returns a Vec of MapRange structs.

This code works on Linux, OSX and Windows. Each operating system has different implementations, but the functions and struct's for each OS share the same interface - so this can be used generically across operating systems.

Note: on OSX this requires root access, and even with root will still not work on processes that have System Integrity Protection enabled (anything in /usr/bin for example).

Example

use proc_maps::{get_process_maps, MapRange, Pid};

let maps = get_process_maps(123456 as Pid).unwrap();
for map in maps {
   println!("Filename {:?} Address {} Size {}", map.filename(), map.start(), map.size());
}

Dependencies

~120KB