TaintSpewer#242
Merged
Merged
Conversation
Contributor
Author
|
I have also added the |
Collaborator
|
Looks good to me, works as intended based on our testing :) |
leeN
approved these changes
Dec 6, 2024
This was referenced Dec 10, 2024
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 implements #236 by implementing a TaintSpewer.
It uses existing mechanisms to dump large amounts of information to file, namely the StructuredSpewer:
project-foxhound/js/src/util/StructuredSpewer.h
Line 121 in 725e1d9
This change adds a new structured SpewChannel, the TaintFlowSpewer, which will then dump a StringTaint object to the SPEW_FILE whenever a sink is hit.
To configure, first build with the following flag in your mozconfig:
And then set the following environment variables:
The spewer will be disabled by default.