Don't accidentially generate trigraphs in filewrapper #17
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.
When trying out this library, I ran into the problem of the sandboxee crashing with the following error on optimized builds (debug builds worked fine):
I traced to problem down to a SIGSEGV, when spawning the embedded child and the problem turned out to be, that parts of the embedded data were interpreted as trigraphs by gcc. This PR fixes this problem by emitting \? instead of ? in the filewrapper.