From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3AA753858C5E; Mon, 24 Jul 2023 18:14:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3AA753858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1690222480; bh=7Z3/VUD2Z2jRzKVJghdnzzGB1mbbuD65rfU9wgglq5k=; h=From:To:Subject:Date:From; b=Vgz6dukfBP+eNuO9jLnSa3XQsDUCFRy6Xic9A2NUk71mwqydRtd+9C+rSQhNjW/od GuyECSWWqAL1cLyzqB0apSdb1O/FT9aIFTiJwBXiKZ0v/v9+U54woUk7eAMMtZMHsJ SL2McbA++oU591OKuE8ugR/P5psfhlvAnKB0fXAE= From: "vmakaev at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug dap/30678] New: DAP Server: Extra breakpoint appears when function breakpoint is hit Date: Mon, 24 Jul 2023 18:14:39 +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: normal X-Bugzilla-Who: vmakaev at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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 attachments.created 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=3D30678 Bug ID: 30678 Summary: DAP Server: Extra breakpoint appears when function breakpoint is hit Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: dap Assignee: unassigned at sourceware dot org Reporter: vmakaev at gmail dot com Target Milestone: --- Created attachment 15008 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D15008&action=3Ded= it dap logs and main.rs Repro steps: 1. put breakpoint on main::main 2. launch debugger in VSCode 3. breakpoint is hit 4. in breakpoints window we can see 1 extra breakpoint that persists after session is ended Note that this behaviour isn't observed with lldb dap. In the following video I launch lldb first (which works correctly) and then= gdb with a mentioned bug (see video https://streamable.com/kf6dyr) Attaching logs from both dap servers and main.rs (rustc -g main.rs) --=20 You are receiving this mail because: You are on the CC list for the bug.=