• '_prologue_' is an imaginary function that initialize argc, argv
  
• Solid arrow means call edge
  
• Dotted arrow means return edge
  
• Green arrow means branch (pair of call & return)
  
For details, see II-A.'Backbone-Branch Decomposition' section of our paper

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT have an outgoing edge from 'spy_user', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

If path includes a call edge from 'output_file' to 'output' either in backbone or branch, then path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation to the sink

If path includes a call edge from 'output_marker' to 'output' either in backbone or branch, then path should NOT have an incoming edge to 'output_marker', for the correct taint propagation to the sink

If path includes a call edge from 'output_file' to 'output' either in backbone or branch, then path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation to the sink

If path includes a call edge from 'output_file' to 'output' either in backbone or branch, then path should NOT have an incoming edge to 'output_file', for the correct taint propagation to the sink

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT have an outgoing edge from 'input_new', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

If path includes a call edge from 'output_file' to 'output' either in backbone or branch, then path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation to the sink

If path includes a call edge from 'output_file' to 'output' either in backbone or branch, then path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation to the sink

If path includes a call edge from 'output_file' to 'output' either in backbone or branch, then path should NOT have an incoming edge to 'output_file', for the correct taint propagation to the sink

If path includes a call edge from 'output_marker' to 'output' either in backbone or branch, then path should NOT have an incoming edge to 'output_marker', for the correct taint propagation to the sink

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

Path should NOT include a call edge from 'output_marker' to 'output' in backbone, because there is a string sanitization in the latter node

Path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation toward the sink

Path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation toward the sink

Path should NOT have an incoming edge to 'output_file', because tainted data cannot flow through the node

Path should include one of the following edges :
(1) Call edge from output_file to output
(2) Call edge from output_marker to output,
for the correct taint propagation to the sink

If path includes a call edge from 'output_file' to 'output' either in backbone or branch, then path should include a return edge from 'expand_user_string' to 'output_file' either in backbone or branch, for the correct taint propagation to the sink

If path includes a call edge from 'output_marker' to 'output' either in backbone or branch, then path should NOT have an incoming edge to 'output_marker', for the correct taint propagation to the sink

If path includes a call edge from 'output_file' to 'output' either in backbone or branch, then path should include a return edge from 'grow_user_string_obstack' to 'expand_user_string' either in backbone or branch, for the correct taint propagation to the sink

If path includes a call edge from 'output_file' to 'output' either in backbone or branch, then path should NOT have an incoming edge to 'output_file', for the correct taint propagation to the sink