💻 Software
Why can't we understand the content of a binary file after compiled?
Fresh5 days ago
Mar 15, 20267989 viewsConfidence Score0%
0%
Problem
As far I know, every program consists of a pack of processor instructions with some specific data variables(float, int, char...) to work on the processor registers. So, the first thing that I thought about it(a long time ago) is that if you know that the ASCII value of (just a random example) could…
Error Output
%¨#$¨#
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Canonical Fix
Unverified Fix
New Fix – Awaiting Verification
Fix for: Why can't we understand the content of a binary file after compiled?
Low Risk
First, registers don't have addresses. Each instruction in any assembly language translates to an opcode. Opcodes in x86 can be one, two, three, or even more bytes (in some other processors they are "fixed-width"). Usually the opcode indentifies the…
Awaiting Verification
Be the first to verify this fix
Sign in to verify this fix