You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When binary is analyzed by rizin, a function could have 2 names:
Real name, for example strcpy
The name defined by Rizin. like sym.strcpy
When researcher uses command ii, Rizin shows real name:
[<addr>]> ii
nth vaddr bind type lib name
----------------------------------------------------------------
170 ---------- GLOBAL NOTYPE __kfifo_out_peek
171 ---------- GLOBAL NOTYPE strcpy
However, AFAIK, the other commands of rizin are using Rizin's name. For example: pdf @ sym.strcpy or axt @ sym.strcpy
The problems:
When a binary is analyzed by rizin, researcher must memorized the way Rizin makes name. And it's not 100% sure that the name made by rizin follows that format
In some big binary, the list of symbols could be very long. It's not very easy to use double tab to show suggest, especially for the axt command.
Describe the solution you'd like
Rizin has a command that shows the real name and rizin's name. For example <command that shows name> strcpy -> sym.xx.yy.strcpy, And <command> sym.xxx.yyy.strcpy -> strcpy.
Command ii and similar should show both real name and rzin's name
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When binary is analyzed by rizin, a function could have 2 names:
strcpy
sym.strcpy
When researcher uses command
ii
, Rizin shows real name:However, AFAIK, the other commands of rizin are using Rizin's name. For example:
pdf @ sym.strcpy
oraxt @ sym.strcpy
The problems:
axt
command.Describe the solution you'd like
<command that shows name> strcpy
->sym.xx.yy.strcpy
, And<command> sym.xxx.yyy.strcpy
->strcpy
.ii
and similar should show both real name and rzin's nameThe text was updated successfully, but these errors were encountered: