mapdump
Mapdump is a simple command-line tool that analyzes binaries to examine memory usage. It is built mainly for embedded C code.
installation
You can download & install mapdump via pip:
$ pip3 install mapdump
You can also download and use mapdump by cloning this repo:
$ git clone https://github.com/sorjente/mapdump
$ cd mapdump/
$ python3 -m mapdump <my_binarys_map.map>
usage
Note: custom options coming soon!
Using mapdump is very simple; you only need to provide it with the .map file corresponding to the binary you want
to analyze. Let's say I want to analyse hello_world.map:
$ mapdump hello_world.map
FLASH @ 0x0008000000 (524288 bytes)
****************************************
build/startup_stm32l452.o [460 bytes, 31.94% of FLASH space used]
lib_a-memcpy.o (/usr/lib/gcc/arm-none-eabi/6.3.1/../../../arm-none-eabi/lib/thumb/v7e-m/fpv4-sp/hard/libc.a) [308 bytes, 21.39% of FLASH space used]
rcc.o (./libopencm3/lib/libopencm3_stm32l4.a) [220 bytes, 15.28% of FLASH space used]
lib_a-memset.o (/usr/lib/gcc/arm-none-eabi/6.3.1/../../../arm-none-eabi/lib/thumb/v7e-m/fpv4-sp/hard/libc.a) [156 bytes, 10.83% of FLASH space used]
build/main.o [116 bytes, 8.06% of FLASH space used]
gpio_common_f0234.o (./libopencm3/lib/libopencm3_stm32l4.a) [68 bytes, 4.72% of FLASH space used]
flash_common_all.o (./libopencm3/lib/libopencm3_stm32l4.a) [36 bytes, 2.50% of FLASH space used]
flash_common_idcache.o (./libopencm3/lib/libopencm3_stm32l4.a) [32 bytes, 2.22% of FLASH space used]
rcc_common_all.o (./libopencm3/lib/libopencm3_stm32l4.a) [26 bytes, 1.81% of FLASH space used]
gpio_common_all.o (./libopencm3/lib/libopencm3_stm32l4.a) [18 bytes, 1.25% of FLASH space used]
dev notes
Tests can (and should be!) run with the following command:
$ python3 -m unittest discover -s mapdump/tests
Metadata
Release files for mapdump 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mapdump-1.0.1.tar.gz | 6.2 kB | Without provenance | Details for mapdump-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mapdump-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for mapdump-1.0.1-py3-none-any.whl |
Total release size: 25.6 kB
Release files / mapdump-1.0.1.tar.gz
| Download URL | mapdump-1.0.1.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
000631dd417473860f13b3553081d7475303bfff90d429e96d0320f768b54fd1
|
|
BLAKE2b-256 checksum How to use checksums |
24880077c93270015e959ff17158581cc97a3f12bcb92b5b5b3b7f448b34f825
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.24.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.9.0
|
Release files / mapdump-1.0.1-py3-none-any.whl
| Download URL | mapdump-1.0.1-py3-none-any.whl |
|---|---|
| Size | 19.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
54bd58cb208d9e3671e1ce027978d30f355305785383486ffe161c9091646b6e
|
|
BLAKE2b-256 checksum How to use checksums |
1e16a9e0bb36488711f53c51f856dc6ea9471c89170458fe3c5ec3523be6007c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.24.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.9.0
|
Security for mapdump 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.