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
For cases when the disassembler starts decoding at the wrong address the user needs to have the ability to override where decoding starts. Like in VS you can start disassembly decoding at a given address.
Yeah the disassembly view itself needs to be a bit smarter here. In the meantime you can work around this, if needed, by using the disassembly view rule in the watch window, which will start at a specific address. You can use something like disasm:{arch:x64, size:2048}.
Due to an unrelated bug, you may need to use a function name to form the address in the current version, even if it’s e.g. Function*0 + 1234.
For cases when the disassembler starts decoding at the wrong address the user needs to have the ability to override where decoding starts. Like in VS you can start disassembly decoding at a given address.
Related: Perhaps this technique could be used as a heuristic for finding the beginning of a instruction when symbols are not available (as well as supporting backwards disassembly ?) .
Parallelising Huffman decoding and x86 disassembly by synchronising non-self-synchronising prefix codes
The text was updated successfully, but these errors were encountered: