-
Notifications
You must be signed in to change notification settings - Fork 14.3k
Support disassembling RISC-V proprietary instructions #145793
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,87 @@ | ||
""" | ||
Defines a command, fdis, that does filtered disassembly. The command does the | ||
lldb disassemble command with -b and any other arguments passed in, and | ||
pipes that through a provided filter program. | ||
The intention is to support disassembly of RISC-V proprietary instructions. | ||
This is handled with llvm-objdump by piping the output of llvm-objdump through | ||
a filter program. This script is intended to mimic that workflow. | ||
""" | ||
|
||
import lldb | ||
import subprocess | ||
|
||
filter_program = "crustfilt" | ||
|
||
def __lldb_init_module(debugger, dict): | ||
debugger.HandleCommand( | ||
'command script add -f filter_disasm.fdis fdis') | ||
print("Disassembly filter command (fdis) loaded") | ||
print("Filter program set to %s" % filter_program) | ||
|
||
|
||
def fdis(debugger, args, result, dict): | ||
""" | ||
Call the built in disassembler, then pass its output to a filter program | ||
to add in disassembly for hidden opcodes. | ||
Except for get and set, use the fdis command like the disassemble command. | ||
By default, the filter program is crustfilt, from | ||
https://github.com/quic/crustfilt . This can be changed by changing | ||
the global variable filter_program. | ||
Usage: | ||
fdis [[get] [set <program>] [<disassembly options>]] | ||
Choose one of the following: | ||
get | ||
Gets the current filter program | ||
set <program> | ||
Sets the current filter program. This can be an executable, which | ||
will be found on PATH, or an absolute path. | ||
<disassembly options> | ||
If the first argument is not get or set, the args will be passed | ||
to the disassemble command as is. | ||
""" | ||
|
||
global filter_program | ||
args_list = args.split(' ') | ||
result.Clear() | ||
|
||
if len(args_list) == 1 and args_list[0] == 'get': | ||
result.PutCString(filter_program) | ||
result.SetStatus(lldb.eReturnStatusSuccessFinishResult) | ||
return | ||
|
||
if len(args_list) == 2 and args_list[0] == 'set': | ||
filter_program = args_list[1] | ||
result.PutCString("Filter program set to %s" % filter_program) | ||
result.SetStatus(lldb.eReturnStatusSuccessFinishResult) | ||
return | ||
|
||
res = lldb.SBCommandReturnObject() | ||
debugger.GetCommandInterpreter().HandleCommand('disassemble -b ' + args, res) | ||
if (len(res.GetError()) > 0): | ||
result.SetError(res.GetError()) | ||
result.SetStatus(lldb.eReturnStatusFailed) | ||
return | ||
output = res.GetOutput() | ||
|
||
try: | ||
proc = subprocess.run([filter_program], capture_output=True, text=True, input=output) | ||
except (subprocess.SubprocessError, OSError) as e: | ||
result.PutCString("Error occurred. Original disassembly:\n\n" + output) | ||
result.SetError(str(e)) | ||
result.SetStatus(lldb.eReturnStatusFailed) | ||
return | ||
|
||
print(proc.stderr) | ||
if proc.stderr: | ||
pass | ||
#result.SetError(proc.stderr) | ||
#result.SetStatus(lldb.eReturnStatusFailed) | ||
Comment on lines
+80
to
+84
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I presume this needs to be swapped. Put stderr in the error so that the user will see it. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure the presence of data on stderr means a failure. I'll look into error handling more. |
||
else: | ||
result.PutCString(proc.stdout) | ||
result.SetStatus(lldb.eReturnStatusSuccessFinishResult) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Istr there is a way to add options for custom commands that show up in
help
like built in ones do.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The triple-quote text at the start of the function definition does that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh that's cool.
What I was thinking of means you don't have to format the usage though, it's generated by lldb. I'll have a look for it tomorrow.