GUI implementations for viewing DMCE generated data.
![](https://private-user-images.githubusercontent.com/22773714/287690830-db5bef9a-63ef-4d7d-8fd9-5ba53a9be0b1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAzMTc5OTQsIm5iZiI6MTcyMDMxNzY5NCwicGF0aCI6Ii8yMjc3MzcxNC8yODc2OTA4MzAtZGI1YmVmOWEtNjNlZi00ZDdkLThmZDktNWJhNTNhOWJlMGIxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA3VDAyMDEzNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTdkYzc1ZjIyNTRmNzFjODBhMWQ1OGRmNWZiZDJjYmQ5MTRiNDNjZGNiMDMzNmM2MmZjZGIwMmFmZmI2Nzg1Y2QmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.1l-e4_2Pesahq7poWOAx-EtEt3d0xRxu7NHh0l-zl0U)
Interactive trace GUI used to view DMCE trace bundles (.zip files).
Use together with v2.0.0 of the dmce git, or master / main on both.
To generate an executable, use the Godot editor: https://godotengine.org/download/archive/4.0.4-stable/
- Navigate to Project->Export.
- Select your platform of preference
- Click "Export all" and choose "Release"
$ # Assuming DMCE is installed on your system (https://github.com/PatrikAAberg/dmce)
$ dmce-set-profile trace-mc
$ cd path-to-git
$ dmce
$ # Build and execute program here
$ dmce-trace --bundle [trace buffer file] [ probe references file] [code tree]
The probe references file is generated at the dmce probing pass. Every time a process exits, which has run at least one dmce probe, a trace buffer file is generated. The code tree is the path to the git containing the probed code. Default locations for the first two:
/tmp/$USER/dmce/dmcebuffer.bin
/tmp/$USER/dmce/name-of-git/probe-references.log
If confusion hits you, --help switches are available for most dmce utilities!