From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3BFB83858416; Tue, 9 Jan 2024 17:47:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3BFB83858416 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1704822434; bh=Uio+2ixqmMZkrNe4JeK+kdzpmwGWSOIAyi4o/f0uWfY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SW7b5EiIUEs9kefrfhPDfWKwvbe0Y1/ElK6g4DkWBFGFUav6LO1G4lF02qMEEGS9u A4YtnmHpPWieoDzmvWso5NUWdd8IqasThCt5stSNho3vbWMUINnZQhciqzGWZwz7CG HfezzfrLx1oiNX7sKa9EGUgmJ5NQCOJaAU9R4r3Q= From: "ssbssa at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/28411] breakpoint sets in wrong line and crashes when attempting to RUN or START Date: Tue, 09 Jan 2024 17:47:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ssbssa at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: MOVED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc resolution bug_status Message-ID: In-Reply-To: References: 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=3D28411 Hannes Domani changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ssbssa at sourceware dot o= rg Resolution|--- |MOVED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Hannes Domani --- (In reply to peffyd from comment #0) > In windows GDB is able to start and I am able to view the file, layout sr= c.=20 > When attempting to add breakpoint such as break main or break > sets breakpoint to wrong line. It sets it a few lines below and does not > allow me to set a breakpoint above the line number that is selected. When > attempting to run or start GDB it crashes the terminal. I have attempted = to > run from command prompt and powershell. Both crash! I'm pretty sure this is the issue that Eli first mentioned here: https://sourceware.org/pipermail/gdb-patches/2020-July/170011.html It was a bug in ncurses that was fixed here: https://lists.gnu.org/archive/html/bug-ncurses/2023-02/msg00005.html --=20 You are receiving this mail because: You are on the CC list for the bug.=