From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 17D733858C78; Fri, 19 May 2023 15:06:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 17D733858C78 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1684508769; bh=Vf9v3SoC1gnycT2cyJGA7V+cTRldTxKUj9JhCoAGg3E=; h=From:To:Subject:Date:From; b=COg1r0ljvDD3PJl2VxMs0JOGSptUSz1+cIc7Tls2fW9ZzUoj0l4ZBEAGa6mQ4wBkR dqEjV1HfJry7i/WK2C1SvAMps9Citblncoseb6UiJFAucXw0oVoJqWFN4BrCMaPtPb Rb/7Nlq3VDWdGxH1P3w4X+UsjsRhLsB78RB94XR0= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug dap/30472] New: DAP "repl" evaluation can make gdb unresponsive Date: Fri, 19 May 2023 15:06:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: dap X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30472 Bug ID: 30472 Summary: DAP "repl" evaluation can make gdb unresponsive Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: dap Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- gdb implements the "repl" context for the "evaluate" request by passing the string to gdb as a command. However, if the command is something like "continue", gdb will simply continue -- but the DAP thread will presumably wait, because eval_request uses send_gdb_with_response. At least... I think this should happen. Step 1 would be to write a test for this. Then, if it fails, some solution would have to be found. Perhaps a global flag to automatically treat continue commands as if they had a "&" would work. --=20 You are receiving this mail because: You are on the CC list for the bug.=