Source

gimli /

Filename Size Date modified Message
lua
man
303 B
374 B
3.3 KB
3.4 KB
1.4 KB
3.4 KB
18.4 KB
835 B
2.1 KB
3.9 KB
303 B
7.6 KB
2.7 KB
1.4 KB
27.0 KB
35.6 KB
16.1 KB
58.5 KB
29.6 KB
13.1 KB
1.4 KB
8.5 KB
15.3 KB
4.0 KB
1020 B
5.7 KB
593 B
10.8 KB
3.2 KB
14.7 KB
2.2 KB
24.8 KB
14.7 KB
21.5 KB
6.9 KB
5.8 KB
16.7 KB
7.4 KB
11.7 KB
2.0 KB
21.0 KB
213 B
1.5 KB
16.2 KB
7.1 KB
676 B
255 B
9.7 KB
20.9 KB
23.5 KB
2.0 KB
10.2 KB
3.6 KB
gimli is a crash tracing/analysis framework.

The concept is that an executable can be linked with libgimli to enable
tracing support.

A gimli enabled application may then be run under supervision of a monitor
process that can detect if the application has stalled, and invoke a trace and
then optionally restart the supervised application.

The tracing is carried out by a glider process.  The glider will gather a
stack trace for all threads in the target process and can also load additional
tracing modules to gather even more information about the problem.

For each mapped module in the traced process address space, the glider will
locate a trace module with a corresponding name.  The trace module can
interrogate the target process to find key datastructures and interpret them
into readable information for the trace file.

Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.