drgn/tests
Omar Sandoval baba1ff3f0 libdrgn: make program components pluggable
Currently, programs can be created for three main use-cases: core dumps,
the running kernel, and a running process. However, internally, the
program memory, types, and symbols are pluggable. Expose that as a
callback API, which makes it possible to use drgn in much more creative
ways.
2019-05-10 12:41:07 -07:00
..
__init__.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
dwarf.py Rewrite drgn core in C 2019-04-02 14:12:07 -07:00
dwarfwriter.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
elf.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
elfwriter.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
libdrgn.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
test_dwarf.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
test_language_c.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
test_lexer.py Rewrite drgn core in C 2019-04-02 14:12:07 -07:00
test_object.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
test_path.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
test_program.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
test_serialize.py Fix some linter errors 2019-04-11 15:51:20 -07:00
test_symbol.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00
test_type.py libdrgn: make program components pluggable 2019-05-10 12:41:07 -07:00