Re: Bug in hexdump when offset == file length

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> It's not a bug, it is an undocumented feature, IMO.
> When you give an offset which is larger than the file size, it will wrap
> back.

Then it's still buggy.
[mike@laptop ~]$ dd if=/dev/urandom of=testfile bs=1 count=42
42+0 records in
42+0 records out
42 bytes (42 B) copied, 0.000216179 s, 194 kB/s
[mike@laptop ~]$ hexdump -Cv testfile -s 42
0000002a  bb b0 ba 50 fe 70 f8 d9  f7 96 36 49 e9 74 c7 bd  |...P.p....6I.t..|
0000003a  82 cb 19 64 a6 30 53 29  d2 fa 08 e3 f4 26 7f de  |...d.0S).....&..|
0000004a  bb 2c f2 df 7c a7 8c 6e  66 01                    |.,..|..nf.|
00000054
[mike@laptop ~]$ hexdump -Cv testfile -s 43
0000002a
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux