Using hexdump to check special chars on files

When you suspect on some word that will hide something inside. And I already have compare file.

First thing I will try
>>> diff file1 file2

Then I know more which word, so I
>>> grep file1

And I'm not sure what wrong with it , I will
>>> grep file1 | hexdump -C

got thing like
00000000  48 65 6c 6c 6f 20 48 6f  77 20 61 72 65 20 79 6f  |Hello How are yo|00000010  75 20 74 6f 64 61 79 0a  0a                       |u today..|00000019

But I think it useless, I decide to
>>> grep file1 | hexdump -c

got this
0000000   H   e   l   l   o       H   o   w       a   r   e       y   o
0000010   u       t   o   d   a   y  \n  \n                            
0000019

the default thing is here0000000 6548 6c6c 206f 6f48 2077 7261 2065 6f79
0000010 2075 6f74 6164 0a79 000a               

0000019

 That's it. Thank Kirit :)

Comments

Post a Comment

Popular posts from this blog

Return Code 127

Exit codes and kill-job signals The exit code from a batch job is a standard Unix termination status, the same sort of number you get in a shell script from checking the " $? " variable after executing a command. Typically, exit code 0 (zero) means successful completion. Codes 1-127 are typically generated by your job itself calling  exit()  with a non-zero value to terminate itself and indicate an error. In BaBar we don't make very much use of this. The most common such value you might see is 64, which is the value used by Framework to say that its event loop is being stopped before all the requested data have been read, typically because time ran out. In recent BaBar releases you might also see 125, which we use as a code for a generic "severe error"; the job log should contain a message stating what the error was. Exit codes in the range 129-255 represent jobs terminated by Unix " signals ". Each type of signal has a number, and what's r
Read more