Timeline for How do I compare binary files in Linux?
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 3 at 19:19 | comment | added | Hashim Aziz | This was exactly the solution I needed because it was the closest to HxD's output. | |
Jun 22, 2023 at 4:33 | comment | added | Gabriel Staples |
For comparing two hex files like this, the GUI program meld works really nice for this! sudo apt install meld , then meld file1.hex file2.hex . I like to make it my git difftool too.
|
|
Jun 23, 2021 at 22:33 | review | Suggested edits | |||
Jun 24, 2021 at 5:57 | |||||
Feb 15, 2018 at 13:37 | history | edited | akira | CC BY-SA 3.0 |
deleted 7 characters in body
|
Apr 4, 2015 at 20:38 | comment | added | Ciro Santilli OurBigBook.com |
This command does not work well for byte addition removal, as every line that follows will be misaligned and seen as modified by diff . The solution is to put 1 byte per line and remove the address column as proposed by John Lawrence Aspden and me.
|
|
Nov 15, 2014 at 23:26 | comment | added | natevw |
This worked great for me (with opendiff on OS X instead of vimdiff ) — the default view xxd provides keeps the diff engine on track comparing byte-by-byte. With plain (raw) hex simply column-fit with fold , diff would try to fold/group random stuff in the files I was comparing.
|
|
Jun 8, 2014 at 9:00 | history | edited | Peter Mortensen | CC BY-SA 3.0 |
Copy edited.
|
Mar 22, 2013 at 3:47 | comment | added | Robert Calhoun |
Nice. I'm on an embedded system that uses BusyBox and there is no cmp , but hexdump + diff works like a charm.
|
|
Mar 30, 2010 at 4:45 | comment | added | akira | with vimdiff it is, it will color the bytes in the lines where the two 'files' differ | |
Mar 29, 2010 at 16:33 | comment | added | Dennis Williamson |
In Bash: diff <(xxd b1) <(xxd b2) but the output format of this (or yours) is nowhere near what the OP asked for.
|
|
Mar 29, 2010 at 16:07 | history | answered | akira | CC BY-SA 2.5 |