Ag argument handling + fix agj @ 0 #10175
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #8385 and fixes #9716
Now ag* commands correctly support arguments (there are some exceptions, like for example the import graph, but the ag? help specifies which commands don't take any arguments).
Also, agj and other commands won't print all the functions of the file when provided with the 0 argument: now the special address is
UT64_MAX
(0xffffffffffffffff
or-1
) that was already used byagC
global callgraphAlso, global graphs now work only in the
[graph.from, graph.to]
range.