RE: [sarif] More threadFlowLocation.kind values

I’d suggest making the first two concepts more generic. Entry points may occur at the driver or dynamic linked library level, for example, for some checkers. The following names might help make these a bit more general purpose

entryPoint

unloadOrExit

‘terminate’ might be another option.

From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On Behalf Of Larry Golding (Comcast)
Sent: Monday, October 1, 2018 2:54 PM
To: 'OASIS SARIF TC Discussion List' <sarif@lists.oasis-open.org>
Subject: [sarif] More threadFlowLocation.kind values

Michael provided feedback on the change draft that restores threadFlowLocation.kind (Issues #194 and #202, pushed from TC #24 to TC #25 for lack of time):

Documents/ChangeDrafts/Active/sarif-v2.0-issues-194-202-threadFlowLocation-changes.docx

He requested some additional values:

"applicationEntryPoint": This location is an entry point to the application.
"applicationExit": This location is a point of exit from the application.
"branchFalse": At this location, a branch in the execution path occurred because the branch condition evaluated to false.
"branchTrue": At this location, a branch in the execution path occurred because the branch condition evaluated to true.
NOTE: Plain “branch” still exists.
"exceptionFilter": At this location, an exception filter was executed.

Remember, the list is not meant to be exhaustive. The spec explicitly permits you to use any value you want if the defined values don’t meet your needs.

Thanks,

Larry

sarif message