)]}'
{
  "commit": "be6276e0aed1f2df8f771d9823b6c8fea29e6a66",
  "tree": "4fe6cbb061a3e3222b057e31b09abd08806671a1",
  "parents": [
    "b64dc199b01de38858c853c434c278a51fe890cb"
  ],
  "author": {
    "name": "Kevin Buettner",
    "email": "kevinb@redhat.com",
    "time": "Wed Oct 19 19:36:07 2022 -0700"
  },
  "committer": {
    "name": "Kevin Buettner",
    "email": "kevinb@redhat.com",
    "time": "Wed Oct 19 19:40:33 2022 -0700"
  },
  "message": "Allow debugging of runtime loader / dynamic linker\n\nAt present, GDB does not allow for the debugging of the runtime loader\nand/or dynamic linker.  Much of the time, this makes sense.  An\napplication programmer doesn\u0027t normally want to see symbol resolution\ncode when stepping into a function that hasn\u0027t been resolved yet.\n\nBut someone who wishes to debug the runtime loader / dynamic linker\nmight place a breakpoint in that code and then wish to debug it\nas normal.  At the moment, this is not possible.  Attempting to step\nwill cause GDB to internally step (and not stop) until code\nunrelated to the dynamic linker is reached.\n\nThis commit makes a minor change to infrun.c which allows the dynamic\nloader / linker to be debugged in the case where a step, next, etc.\nis initiated from within that code.\n\nWhile developing this fix, I tried some approaches which weren\u0027t quite\nright.  The GDB testusite definitely contains tests which FAIL when\nit\u0027s done incorrectly.  (At one point, I saw 17 regressions!) This\ncommit has been tested on x86-64 linux with no regressions.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2e462be5ba7033c4936bec8b181068c7dae8226b",
      "old_mode": 33188,
      "old_path": "gdb/infrun.c",
      "new_id": "9a9f42fc903def3641a55b1a0b2d41698f0c1c96",
      "new_mode": 33188,
      "new_path": "gdb/infrun.c"
    }
  ]
}