Menu
▾
▴
Tree [000615] master / History
| File | Date | Author | Commit |
|---|---|---|---|
| examples | 2019-01-02 |
Hannes Domani
|
[2d4238] unicode support |
| include | 2019-01-02 |
Hannes Domani
|
[2d4238] unicode support |
| libdwarf | 2021-11-07 |
Hannes Domani
|
[e92e72] allow static build of libdwarf |
| mgwhelp | 2021-11-21 |
Hannes Domani
|
[93f24f] remove redundant if-conditions |
| src | 2021-11-10 |
Hannes Domani
|
[c8f146] support DWARF5 rnglists |
| zlib | 2017-01-18 |
Hannes Domani
|
[6b2428] upgrade to zlib-1.2.11 |
| .gitignore | 2018-01-18 |
Hannes Domani
|
[3a1b0b] GitIgnore user files and 7z archives |
| LICENSE.txt | 2014-05-12 |
Hannes Domani
|
[adadfb] remove trailing spaces |
| Makefile | 2024-01-27 |
Hannes Domani
|
[000615] set version 2.3-git |
| README.md | 2015-09-23 |
Hannes Domani
|
[547b7d] convert README to markdown syntax |
| dwarfstack.qbs | 2021-11-07 |
Hannes Domani
|
[e92e72] allow static build of libdwarf |
Read Me
dwarfstack
dwarfstack aims to provide a simple way to get meaningful stacktraces.
Only windows executables (mingw-gcc) are supported.
It uses the debug information (if available) of the executables and converts
the addresses into source file/line information.
To get a better picture, check out the examples.
compilation:
make
installation:
make PREFIX=/your/install/path
notes:
If you need a full stacktrace for release builds, you should consider
using -fno-omit-frame-pointer (and maybe even
-fno-optimize-sibling-calls / -fno-schedule-insns2).
Otherwise, depending on the situation (like gcc version), some frames
might be missing.
