)]}'
{
  "commit": "c7224db7af39652f36fd538ac997eb40cc79d770",
  "tree": "f04a5221ce6fc168d64d457d65b4ba1dcb480b6c",
  "parents": [
    "ca362799ee0ab2bd4d4ea4f521726fefbfbad738"
  ],
  "author": {
    "name": "Tom Tromey",
    "email": "tom@tromey.com",
    "time": "Sat Oct 14 12:31:31 2023 -0600"
  },
  "committer": {
    "name": "Tom Tromey",
    "email": "tom@tromey.com",
    "time": "Sun Oct 29 10:34:51 2023 -0600"
  },
  "message": "Pre-read .debug_aranges section\n\nWhile working on background DWARF reading, I found a race case that I\ntracked down to the handling of the .debug_aranges section.  Currently\nthe section data is only read in after the CUs have all been created.\nHowever, there\u0027s no real reason to do this -- it seems fine to read it\na little earlier, when all the other necessary sections are read in.\n\nThis patch makes this change, and updates the\nread_addrmap_from_aranges API to assert that the section is read in.\n\nThis patch slightly changes the read_addrmap_from_aranges API as well,\nto reject an empty section.  This seems better to me than what the\ncurrent code does, which is try to read an empty section but then do\nno work.\n\nRegression tested on x86-64 Fedora 38.\n\nReviewed-By: Guinevere Larsen \u003cblarsen@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2e5067efb3d73ba16997d664b1fb0ebbdf4be36c",
      "old_mode": 33188,
      "old_path": "gdb/dwarf2/read-debug-names.c",
      "new_id": "89f5df6df900c21c5d43820ce631e2e8d0bb481e",
      "new_mode": 33188,
      "new_path": "gdb/dwarf2/read-debug-names.c"
    },
    {
      "type": "modify",
      "old_id": "ea0b2328a3e43309b3aa265069c858f698981adf",
      "old_mode": 33188,
      "old_path": "gdb/dwarf2/read.c",
      "new_id": "c8e21aa9c2d55a70acfe84d8c18c9832a7581637",
      "new_mode": 33188,
      "new_path": "gdb/dwarf2/read.c"
    }
  ]
}