Closed cuviper closed 9 years ago
FWIW, binutils' readelf isn't annoyed by this:
Offset Begin End
00000000 ffffffffffffffff 0000000000000000 (base address)
00000000 ffffffff81000000 ffffffff810001c7
00000000 ffffffff81d4b000 ffffffff81d4b205
00000000 <End of list>
00000040 ffffffff81d4b222 ffffffff81d4b248
00000040 ffffffff81d4b252 ffffffff81d4b255
00000040 <End of list>
00000040 ffffffff81d4b222 ffffffff81d4b248
00000040 ffffffff81d4b252 ffffffff81d4b255
00000040 <End of list>
And the raw dump is:
Hex dump of section [38] '.debug_ranges', 3274176 bytes at offset 0x9c6a570:
0x00000000 ffffffff ffffffff 00000000 00000000 ................
0x00000010 00000081 ffffffff c7010081 ffffffff ................
0x00000020 00b0d481 ffffffff 05b2d481 ffffffff ................
0x00000030 00000000 00000000 00000000 00000000 ................
0x00000040 22b2d481 ffffffff 48b2d481 ffffffff ".......H.......
0x00000050 52b2d481 ffffffff 55b2d481 ffffffff R.......U.......
0x00000060 00000000 00000000 00000000 00000000 ................
0x00000070 6ab3d481 ffffffff 72b3d481 ffffffff j.......r.......
...
Thanks. This sort of looks like elfutils problem, but I'll need to look more closely.
This will be fixed in elfutils upstream.
I encountered this error:
That CU as shown by eu-readelf is:
The next CU has range list 250, so this one contains:
I suppose the "garbage" is the issue tripping up dwgrep...