tree e6646cc328b2730a7fe4adb4dfd88a4a2429e2ba
parent 8ddada41df0488358373cff1d31a47e5ef4961e0
author Jacob Lalonde <jalalonde@fb.com> 1750210635 -0700
committer GitHub <noreply@github.com> 1750210635 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJoUhhLCRC1aQ7uu5UhlAAAxJEQABXOxvn9DBjPD7CM/hbp0olI
 l4Chrb+aCxXQ9fy+ZQTpj5+NiWMXOCCIZQdo92tzaPTuVkBK85zi/gzyn+dyOOE8
 W+A8rElAZGdQ5YiBZzJB291D2m0HuAP1ehord9LUQHpNMkDCqHoCKJphzBYAt0V9
 SgwGUdRlkca5Ebcokm5RrDEpKaquQ+ZAQmDFNJ1NXPmogv0LmhEz/P/OZO9A8SiO
 0fjaHnskG1ejs/Ltbp6OEnE8a0DoS18N0FSm5BG1KwKWbwYGFIVdxDPxauCqH8ia
 ZqVkFwufFUY333/BzdAQqHkT0jtmrkW/rUPcP9wC/3yZwSZeMa8DTj8mfdP4BBvH
 kHfTpsMzNEhZVw209Li8m3c3IjYXep4+iQYuR2ZSUoS5RNaWdX85Dl2ZXcKHe/v5
 wccjb1I3GZtur3Q2O0JlUKhDfR1wtBS1jvcEHGZYgMf4hTrCiEM5sS8nJRie9yE7
 bWc+c+DCb47vwCWkp2buEF0tCPol0VHugiqO9/0q1dxzVMz7ThAexu4ze3rEc7Yy
 qIcH3qQeuO/qnSs78P2WIpRkitFpfdQ6Nssf2m0XJsrmXHaUbKUiW1rmSga6slct
 6Kkx7uz1UTUSsSCXQ0/GjlUSjCaS3AUiigiSJaNGsdpSytikdVR8hLlEDvPmEhl9
 kZq1Ph17UyK5e2qo0boH
 =rKGc
 -----END PGP SIGNATURE-----
 

[lldb][Minidump Parser] Implement a range data vector for minidump memory ranges (#136040)

Recently I was debugging a Minidump with a few thousand ranges, and came
across the (now deleted) comment:

```
  // I don't have a sense of how frequently this is called or how many memory
  // ranges a Minidump typically has, so I'm not sure if searching for the
  // appropriate range linearly each time is stupid.  Perhaps we should build
  // an index for faster lookups.
```

blaming this comment, it's 9 years old! Much overdue for this simple fix
with a range data vector.

I had to add a default constructor to Range in order to implement the
RangeDataVector, but otherwise this just a replacement of look up logic.