3

For example, 

00000200  6E 74 3D 22 49 45 3D 65  64 67 65 22 20 2F 3E 0D   nt="IE=edge" />.
00000210  0A 20 20 20 20 3C 6D 65  74 61 20 6E 61 6D 65 3D   .    <meta name=
eichoa3I
  • 1,512
  • 8
  • 18
  • 29

1 Answers1

7

it's the offset

In general, your file begins at 0x0000h, and then it's shown at 16 bytes each time. So the next address is 0x0010h (that's 16 bytes = 10h bytes).

In your example, you are showing at 200h bytes from the begining, and then 210h bytes from the begining... :)

woliveirajr
  • 4,170
  • 23
  • 32
  • 1
    wouldn't "offset" be the correct term? (offset from start of file, 0 being the start) – horatio Apr 19 '12 at 17:17
  • Wouldn't it just be the same thing.. – cutrightjm Apr 19 '12 at 17:19
  • @horatio Perfect, it's "offset" the most common name. I'll edit my answer, when I was typing it I completly forgot the name and used the generic "address" – woliveirajr Apr 19 '12 at 17:20
  • 1
    @ekaj: not being an expert, I haven't heard "address" used in this respect. One thing I can say though is that "address" implies a qualified location, where "offset" is a relative location. ("123 main street" is an address, "next door" is an offset) – horatio Apr 19 '12 at 17:25
  • Why is hexdump showing 16 bytes at a time? – briankip Apr 01 '16 at 14:36
  • Also how is 16bytes = 10h bytes – briankip Apr 01 '16 at 15:26
  • 3
    @briankip : 16 bytes = it's arbitrary. We hardly use the number 10 when we're dealing with binaries and so on, we tend to use 8 or 16, since they are power of 2. And the number 16, when represented in hexadecimal, is written 10 :) In hexadecimal, you have (...)08,09,0a,0b,0c,0d,0e,0f,10,11(..) – woliveirajr Apr 01 '16 at 17:09