{"push_id":1245209446,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"9ea0c9bc9feb97db7bfcc59c67ce1484f1cbfe04","before":"e41f926ce54c7a5861f0db96c79c0b96f349e68b","commits":[{"sha":"95ae38eed7e3baeeeca300826db3b3948ec03967","author":{"name":"clslgrnc","email":"69bb182b0ae845d9d24529b0e276d14c3b5669d0@users.noreply.github.com"},"message":"Find/Avoid conflict example\n\nThere is a bug in angr/angr/exploration_techniques/explorer.py filter function.\nFind condition is checked before avoid condition at the run level. Thus, if avoid and find addresses are in the same run the path is accepted even if the avoid address is reached before the find address; they do not need to be in the same basic block, consider:\nA\nif (...) then{ B }\nelse{ C }\nD\n\nIf one wants to reach D while avoiding C, AC would be a valid path, because run C is composed of the basic blocks C (avoid) and D (find).\n\ntests_src/ite_FindAvoidConflict.c exhibits such a behavior.","distinct":true,"url":"https://api.github.com/repos/angr/binaries/commits/95ae38eed7e3baeeeca300826db3b3948ec03967"},{"sha":"9ea0c9bc9feb97db7bfcc59c67ce1484f1cbfe04","author":{"name":"Andrew Dutcher","email":"af98c23c46cd7455d5fad04954e1ccfec6b571ab@gmail.com"},"message":"Merge pull request #7 from clslgrnc/master\n\nFind/Avoid conflict example","distinct":true,"url":"https://api.github.com/repos/angr/binaries/commits/9ea0c9bc9feb97db7bfcc59c67ce1484f1cbfe04"}]}
{"actor":{"display_login":"rhelmot"}}