You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was approved for resolution in CSD.1 in the TC meeting of 2/28/2018.
In #92, we introduced properties on the invocation object to specify the locations of files containing the contents of the stdin, stdout, and stderr streams. But many engineering systems redirect both stdout and stderr to the same file. How should SARIF represent that.
The text was updated successfully, but these errors were encountered:
Resolution here: stderr is present, the tool populates it. stderr may be empty in this case. if stderr is not present at all in the SARIF, it is an indicator that it is not separated as a stream and stderr contents may be interleaved with stdout (if present)
This issue was approved for resolution in CSD.1 in the TC meeting of 2/28/2018.
In #92, we introduced properties on the
invocation
object to specify the locations of files containing the contents of thestdin
,stdout
, andstderr
streams. But many engineering systems redirect bothstdout
andstderr
to the same file. How should SARIF represent that.The text was updated successfully, but these errors were encountered: