Value.backward_df_recursive()
Returns the list of all previous points of the current point in the current data flow graph and outside of that.
backward_df_recursive() → APISet[Point]
The function works similarly to Value.backward_df(); the main difference is that in case of Value.backward_df() the function will return backward dataflow point for every point in the Value, while Value.backward_df() returns only those connected with the current Value.
Like all other dataflow (DF) functions, it returns a list/set of Points, which can be instructions or "points" in the code, such as arguments, variables, etc.
Query Example
Consider the following Solidity functions:
function transfer(address recipient,uint256 amount) public virtual override returns (bool) {
_transfer(_msgSender(),recipient,amount);
return true;
}
function _msgSender() internal view virtual returns (address) {
return msg.sender;
}
function _transfer(address sender,address recipient,uint256 amount) internal virtual {
require(sender != address(0),"ERC20: transfer from the zero address");
require(recipient != address(0),"ERC20: transfer to the zero address");
_beforeTokenTransfer(sender,recipient,amount);
uint256 senderBalance = _balances[sender];
require(senderBalance >= amount,"ERC20: transfer amount exceeds balance");
_balances[sender] = senderBalance - amount;
_balances[recipient] += amount;
emit Transfer(sender,recipient,amount);
}In the _transfer function, we want to locate the first require statement and determine the origin of the sender variable across multiple functions:
To do this, we first query for the instruction containing the require statement and then query for sender:
Finally, we call backward_df_recursive() to identify where the sender originates. Glider will transverse from the _transfer() function, transfer() function, and msgSender() functions to identify the sender source.
Example Output

Last updated