)]}'
{
  "commit": "11470e70ea0d692db00285422efa474224727487",
  "tree": "d73bbbff01e90fbb19384ff1aa70d50e6faa2888",
  "parents": [
    "dbca589b8d72316a5884321747b6ab92c6b34dbc"
  ],
  "author": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Tue Feb 14 14:23:27 2023 -0500"
  },
  "committer": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Wed Feb 15 11:58:24 2023 -0500"
  },
  "message": "gdb: store internalvars in an std::map\n\nIn a test downstream in ROCgdb, we had a test case failing when\nGDB_REVERSE_INIT_FUNCTIONS was set.  The test was assuming a particular\norder in the output of \"show convenience\".  And the order changes when\nrunning with GDB_REVERSE_INIT_FUNCTIONS.\n\nI think that a nice way to fix it is to make the output of \"show\nconvenience\" sorted, and therefore stable.  Ideally, I think that the\nthe user-visible behavior of GDB should not change when using\nGDB_REVERSE_INIT_FUNCTIONS.  Plus, it makes the output of \"show\nconvenience\" look nice, not that it\u0027s really important.\n\nImplement this by storing the internal vars in an std::map, which is a\nsorted container.\n\nChange-Id: I1fca7e7877cc984a3a3432c7639d45e68d437241\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1b74a6ecc4ff688046ed9713a3c47c3f10b62fea",
      "old_mode": 33188,
      "old_path": "gdb/value.c",
      "new_id": "34a282b9746508f75ba8b943626381e0246f293c",
      "new_mode": 33188,
      "new_path": "gdb/value.c"
    }
  ]
}