Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with disassembly
Search options not deleted
user 22178
The translation of machine code into a human readable assembly code, also the result of such translation.
1
vote
0
answers
332
views
Pointer disassembly
Consider some disassembly (it does not really matter what it does):
0x4005b6: xor ebx, ebx
0x4005b8: nop dword ptr [rax + rax]
0x4005c0: mov rdx, r13
0x4005c3: mov … rbx*8]
p.s. if it is of any interest, the value of r12 is computed as
0x40058b: lea r12, qword ptr [rip + 0x20087e]
the rip and r12 register is not referenced anywhere else in the wider disassembly …
2
votes
1
answer
3k
views
Disassemblers resolving (ELF) section names
I'm working with linux executables and was just wondering how it is that section names are resolved to addresses upon disassembly of an ELF. … How would I reproduce this if I were to write a disassembly tool + executable analyser myself?
Thanks …