)]}'
{
  "commit": "ee3c07a28be01ff4ab34089b8849aa398cc2d612",
  "tree": "fa93be904491b89cb94a8d10fb0abc673b5782dc",
  "parents": [
    "e53b88b40ed38651b50f954dfe76066822094c15"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Aug 15 14:48:10 2025 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Aug 15 14:48:10 2025 +0200"
  },
  "message": "[gdb/tui] Clear readline buffer on switching to TUI\n\nConsider the following scenario.  We start gdb and type foo:\n...\n$ gdb -q\n(gdb) foo\n         ^\n...\n\nThen we switch to TUI using C-x C-a, and switch back using the same key\ncombination.\n\nWe get back the same, but with the cursor after the prompt:\n...\n(gdb) foo\n      ^\n...\n\nTyping b\u003cENTER\u003e gives us:\n...\n(gdb) boo\n❌️ No default breakpoint address now.\n(gdb)\n...\nwhich means gdb didn\u0027t see \"boo\" here, just \"b\".\n\nSo while \"foo\" is part of the readline buffer when leaving CLI, it\u0027s not upon\nreturning to CLI, but it is still on screen, which is confusing.\n\nFix this by using rl_clear_visible_line in tui_rl_switch_mode to clear the\nreadline buffer when leaving CLI.\n\nThis only reproduces for me with TERM\u003dxterm.\n\nTested on x86_64-linux.\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d30523\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5883d6cad5ed9e2f478ecc824d13e836de6f7aac",
      "old_mode": 33188,
      "old_path": "gdb/tui/tui.c",
      "new_id": "01aee2f178869ca465a20eb749943bf799f33b17",
      "new_mode": 33188,
      "new_path": "gdb/tui/tui.c"
    }
  ]
}