tree 3021a7974a2f83ca451dc4879c9c289068cbb5cb
parent 97b8cec789fe3b8558a6d2b7fac269c5606ab4a3
author David Spickett <david.spickett@linaro.org> 1750843898 +0100
committer GitHub <noreply@github.com> 1750843898 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJoW8H6CRC1aQ7uu5UhlAAAi8QQAEvJA4ENG1F35a20VOy/y65u
 KylkXGOwb88mMAYE6g88lFq2psFmC8IkH4QWnb8tBRO+0kEJy8sUmfNirKu6Mx9N
 qnS4EU5elYDuLjX5Lt19SkPzdqT/cmywS/QFeNSL74nAcRsfjUSirXBWy3APodBd
 Ax+dh+kjDQ/KNOdCwXrl/owkqDyjEAn3eWwUpZEsDmHL6r3h1ZeRK2cERTlFezJp
 5OwyafY2awLi5mkATXBhiQrXcip4W/OS4e7qvO4P9NrduzLVHcZwftafA0VsmG5P
 orT9DYtCU1IIeK9eiqPfGku3T/6R1hTv7HMr+djQnfyDUtdOFuryECA/UI68+ktw
 sI+o766XIPGJnwWiYQ0F/By6mkOo6Trqj4PH0P5rcoZrSmPYzEWEkQc3tdoETcN7
 Nmw3Ssx7MlhHBWwT7Ir7MrpVpCjTvlr4uFpCqgdjv0OqHbMIfpMb/kCzmKC1DzHu
 +H6D+5E4S4a5ZctTSFbBzNaKG93w+V8hgCMaAfw26L859GGxEawEDOcRskvo4mVw
 BY+gPE9EvdPbMj4EM8FFtwDLKEfk9OFnZssmGgIPgS9IusRspMaRMdCKM7ahBlrL
 aflVp+RYwQuTK1jRStQeUuRJimC6t2p/4NH0BBEKd6Az0ilyEWkXRa4P3RKx7GIC
 L7hd2yKP77scWnThpMQu
 =duVD
 -----END PGP SIGNATURE-----
 

[lldb][AArch64] Handle core file tag segments missing tag data (#145338)

In the same way that memory regions may be known from a core file but
not readable, tag segments can also have no content. For example:
```
$ readelf --segments core
<...>
Program Headers:
  Type           Offset             VirtAddr           PhysAddr
                 FileSiz            MemSiz              Flags  Align
<...>
  LOAD           0x0000000000002000 0x0000ffff93899000 0x0000000000000000
                 0x0000000000000000 0x0000000000001000  RW     0x1000
<...>
  LOPROC+0x2     0x0000000000008000 0x0000ffff93899000 0x0000000000000000
                 0x0000000000000000 0x0000000000001000         0x0
```
This happens if you have a restricted coredump filter or size limit.

The area of virtual memory this segment covers is 0x1000, or 4096 bytes
aka one tagged page. It's FileSiz would normally be 0x80. Tags are
packed 2 per byte and granules are 16 bytes. 4096 / 16 / 2 = 128 or
0x80.

But here it has no data, and in theory a corrupt file might have some
data but not all. This triggered an assert in
UnpackTagsFromCoreFileSegment and crashed lldb.

To fix this I have made UnpackTagsFromCoreFileSegment return an expected
and returned an error in this case instead of asserting. This will be
seen by the user, as shown in the added API test.