This repository has been archived by the owner on Jul 22, 2020. It is now read-only.
calltrace.plugin
Klemens David Morgenstern edited this page Apr 4, 2018
·
1 revision
The invocation does look as follows:
metal.runner --lib=metal-calltrace test.exe
By default the plugin will output all the calltraces at initialization and deinitialization (including the result) and all the function calls while any calltrace is registered.
This section describes the usage of the dbg-runner
. We will assume that the command is available, though you might need to either use the absolute path or
add the path to the PATH
variable.
Here's an overview of all parameters the calltrace adds:
[note Plugins can add other parameters]
Option | Description | Value type | Default |
---|---|---|---|
--metal-calltrace-sink |
Set the sink to a file, it uses stdout when not set |
string | none |
--metal-calltrace-format |
The format of the output [hrf, json] | string | hrf |
--metal-calltrace-all |
Output all function calls, by default only those traced are outputted. | bool switch | none |
--metal-calltrace-timestamp |
Try to use the timestamp, if available | bool switch | none |
--metal-calltrace-minimal |
Minimal will only output the results of calltraces, not function calls. | multiple strings | none |
--metal-calltrace-depth |
The depth of the calltrace, if set it will skip function called deeper nested that this | int |
none |
--metal-calltrace-manual-disable |
Use the debugger to disable the tracing when obtaining the timestamp | bool switch | none |
- Overview
- Runner Introduction
- Runner Invocation
- Runner Plugins
- Runner Extender
- Runner FAQ
- Runner Reference
- Unit Introduction
- Unit Tutorial
- Unit FAQ
- Unit Reference
- Calltrace Introduction
- Calltrace Tutorial
- Calltrace FAQ
- Calltrace Plugin
- Calltrace Reference
- Serial Introduction
- Serial Tutorial
- Serial Invocation
- Serial Reference