)]}'
{
  "commit": "1ba0c1720eb0de2d0f3abf84c0b128d10af520d1",
  "tree": "47515d331a39e868510266d72f29267b30b00399",
  "parents": [
    "b8adde8ddec9ff62a21564fa8020b5463e70d4de"
  ],
  "author": {
    "name": "Jason Wessel",
    "email": "jason.wessel@windriver.com",
    "time": "Wed Sep 21 13:07:47 2011 -0700"
  },
  "committer": {
    "name": "Jason Wessel",
    "email": "jason.wessel@windriver.com",
    "time": "Thu Mar 22 15:07:16 2012 -0500"
  },
  "message": "kdb: Add message about CONFIG_DEBUG_RODATA on failure to install breakpoint\n\nOn x86, if CONFIG_DEBUG_RODATA is set, one cannot set breakpoints\nvia KDB.  Apparently this is a well-known problem, as at least one distribution\nnow ships with both KDB enabled and CONFIG_DEBUG_RODATA\u003dy for security reasons.\n\nThis patch adds an printk message to the breakpoint failure case,\nin order to provide suggestions about how to use the debugger.\n\nReported-by: Tim Bird \u003ctim.bird@am.sony.com\u003e\nSigned-off-by: Jason Wessel \u003cjason.wessel@windriver.com\u003e\nAcked-by: Tim Bird \u003ctim.bird@am.sony.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "20059ef4459a4ff293428337d9936ff438a8eb96",
      "old_mode": 33188,
      "old_path": "kernel/debug/kdb/kdb_bp.c",
      "new_id": "8418c2f8ec5dd255d18794ca13cf895a3b588a76",
      "new_mode": 33188,
      "new_path": "kernel/debug/kdb/kdb_bp.c"
    }
  ]
}