Make backtraces as feature, enabled by default #214
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes backtraces optional, while enabled by default.
Sometimes it can be very desireable to disable them totally.
E.g. when fuzzing, with backtraces you get unstable 100-5000 execs per second, but without them it is 50k execes per second (from OER and with AFL) for some simple types.
There might be some other scenarios where performance gets priority over exact error sources.