)]}'
{
  "commit": "37563b8beb5df0a7358fa6780a63edf5d3c447a1",
  "tree": "de6acd47b063a474755f91fc163f8b2009db8d1e",
  "parents": [
    "0f0c6492bd1b9711e22abf7235f8c60405ac907f"
  ],
  "author": {
    "name": "Sébastien Darche",
    "email": "sdarche@efficios.com",
    "time": "Mon Oct 20 15:07:33 2025 -0400"
  },
  "committer": {
    "name": "Sébastien Darche",
    "email": "sdarche@efficios.com",
    "time": "Tue Oct 28 09:43:30 2025 -0400"
  },
  "message": "gdb: lookup minsym using section in find_sal_for_pc_sect\n\nThe find_sal_for_pc_sect function attempts to find the line that is\nclosest to a pc+section in the available symbols. One of the first thing\nthe function does is search for a bound minimal symbol corresponding to\nthat pc. In its original version, the lookup is performed by\nlookup_minimal_symbol_by_pc, discarding the section. This is misleading\nand may cause issues with overlay debugging if a second minsym with the\nsame pc (but a different section) can be found -- although this is only\nin theory after inspecting the code, as I have no way to test this on a\nsystem supporting overlays.\n\nThis should have no observable effects for the end user. One slight\nbenefit is that we can avoid a section lookup inside\nlookup_minimal_symbol_by_pc_section if the caller does provide a\nsection.\n\nSince the section is already passed as an argument to the function, the\nproposed change forwards this section to the minsym lookup section.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\nChange-Id: I86a16bf397ea7167d3e9c7db79b8d7901fad1a97\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2b54d245b86a5ec7342926029ab5351426cb33e2",
      "old_mode": 33188,
      "old_path": "gdb/symtab.c",
      "new_id": "0ddb25f2879997abe8ab447739c286696a3472a4",
      "new_mode": 33188,
      "new_path": "gdb/symtab.c"
    }
  ]
}