)]}'
{
  "commit": "718b36fead887693158396b948d7f409b987c053",
  "tree": "12a0530f95c0af1dcec1370e41177313240d10d7",
  "parents": [
    "9939a5ae6e80626c29fe602d366e9eece9652d06"
  ],
  "author": {
    "name": "Don Breazeal",
    "email": "donb@codesourcery.com",
    "time": "Wed Feb 10 15:41:55 2016 -0800"
  },
  "committer": {
    "name": "Don Breazeal",
    "email": "donb@codesourcery.com",
    "time": "Wed Feb 10 15:42:15 2016 -0800"
  },
  "message": "Fix \u0027-data-read-memory-bytes\u0027 typo/assertion\n\nBackported to the 7.10 branch per this thread:\nhttps://www.sourceware.org/ml/gdb-patches/2016-02/msg00134.html\n\nThis patch fixes a typo in target.c:read_memory_robust, where\nit calls read_whatever_is_readable with the function arguments\nin the wrong order.  Depending on the address being read, it\ncan cause an xmalloc with a huge size, resulting in an assertion\nfailure, or just read something other than what was requested.\n\nThe problem only arises when GDB is handling an MI\n\"-data-read-memory-bytes\" request and the initial target_read returns\nan error status.  Note that read_memory_robust is only called from\nthe MI code.\n\ngdb/ChangeLog:\n\n\t* gdb/target.c (read_memory_robust): Call\n\tread_whatever_is_readable with arguments in the correct order.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "24589c833ac94795e539816ba9171453e9adf951",
      "old_mode": 33188,
      "old_path": "gdb/ChangeLog",
      "new_id": "220625953c051cd31e9a1ed3d446cb614dd8b681",
      "new_mode": 33188,
      "new_path": "gdb/ChangeLog"
    },
    {
      "type": "modify",
      "old_id": "4dd991a93148c70f79861eba5b81856942034473",
      "old_mode": 33188,
      "old_path": "gdb/target.c",
      "new_id": "4731491c28b1ce06fe807a257547372c569b100c",
      "new_mode": 33188,
      "new_path": "gdb/target.c"
    }
  ]
}