-
Notifications
You must be signed in to change notification settings - Fork 14
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
Feature Request: Provide an offset for disassembly #226
Comments
This is for memory disassembly or file ? |
If you're disassembling from a symbol address you can apply an offset by writing it as an expression e.g. Hopefully this handles your use case. @prb28 the help text could do with updating to document that expressions are supported. Also the As far as having the disassembler ignore errors, we're really limited by Capstone, which does appear to just give up when it reaches invalid instructions. |
@grahambates yes, I've missed that syntax change you've added. If you want you can add a pr of course, but I can do it too. Capstone is a limitation here. I don't know if there is a better pure JavaScript choice. |
Yeah I agree that writing a new disassembler in JS is not realistic and Capstone is the best option, especially now that WASM means we don't have a dependency on the native binary. I'm also not sure that Capstone's behaviour is necessarily wrong in this case. |
Never tried to disassemble a boot block. And didn't know radare2 tool. I'll try it to see if it can be improved. |
When performing a disassembly if the start bytes are not code then the disassembly fails. Could you please add an option to either provide an offset to disassemble from or a way for the disassembly to ignore errors so any headers are skipped over.
The text was updated successfully, but these errors were encountered: