Re: Bug in hexdump when offset == file length

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

 



On Thu, Nov 26, 2009 at 2:04 PM, Mike Smith <scgtrp@xxxxxxxxx> wrote:
> This seems to dump from the start of the file if dsdt2.aml is exactly
> 0xB13C bytes:
>
> [mike@laptop ~]$ hexdump -Cv dsdt2.aml -s 0xB13C |head -2
> 0000b13c  44 53 44 54 3a 58 00 00  01 98 54 4f 53 49 4e 56  |DSDT:X....TOSINV|
> 0000b14c  54 4f 53 49 4e 56 30 30  01 00 00 00 49 4e 54 4c  |TOSINV00....INTL|

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.
--
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