)]}'
{
  "commit": "aac60a978e2620037e4b034386cbc6ef65f8e4aa",
  "tree": "0bbe89210090323bdfa9eed2fcb6a3af0fcfc6d2",
  "parents": [
    "a2827364e2bf19910fa5a54364a594a5ba3033b8"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Fri Sep 08 15:50:19 2023 +0100"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Thu Sep 28 15:33:13 2023 +0100"
  },
  "message": "gdb: remove unnecessary notification of executable_changed observer\n\nThis commit continues the work of the previous two commits.\n\nMy goal, in the next couple of commits, is to expose the\nexecutable_changed observable in the Python API as an event.  However,\nbefore I do that I want to remove the use of the executable_changed\nobservable from the reread_symbols function in symfile.c as this use\nisn\u0027t directly associated with a change of the executable file, and so\nseems wrong.\n\nIn the previous two commits I have removed all users of the\nexecutable_changed observer as I believe those users can, and should,\nactually be listening for the new_objfile observable instead, so now\nthere are no users of the executable_changed observable.\n\nAs such, I think removing the use of executable_changed from the\nfunction reread_symbols is perfectly safe, and correct.  At this point\nthe executable has not been changed, so we shouldn\u0027t be sending an\nexecutable_changed notification, and, as there is nobody listening to\nthis observable, we can\u0027t break anything by removing this call.\n\nThere should be no user visible changes after this commit.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "76b5e1b8fe7e8df825fe621e3789e77892342899",
      "old_mode": 33188,
      "old_path": "gdb/symfile.c",
      "new_id": "47e815448ed6a617f01f34ec41a1577b05ae2671",
      "new_mode": 33188,
      "new_path": "gdb/symfile.c"
    }
  ]
}