From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D94783858D1E; Tue, 29 Nov 2022 20:29:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D94783858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669753793; bh=fuP19kOhq/uGiuKuBizyOkNsDfLb88XMao0PktVweb0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vR5b2012heYbO2fUCk3Z7yNg2zC6ZQzY8RO/d8AG7BlQwNBBwxDks7B8O97EZBAmB iuDKorE0p2m1AWZHRh2k8D7WhGBZRtWPAazRBIDrPHg/32G7rlPyx8vpdYbHMdmyv9 /Fk6u1t1kaIG3DEMFFh/mQ3jYQtFTi6pZxZYwPtE= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/21774] Ubuntu: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Tue, 29 Nov 2022 20:29:53 +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: 7.11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: WAITING 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: everconfirmed bug_status cc cf_reconfirmed_on 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=3D21774 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |WAITING CC| |tromey at sourceware dot o= rg Last reconfirmed| |2022-11-29 --- Comment #3 from Tom Tromey --- > I use gdb to debug a kernel module, when the code hits the breakpoints, a= nd=20=20 > i type 'c' ,then the same internel-error as follow. We'd need more info to know what is going on here. One possibility is a bug in the gdbserver you're using (presumably built into the kernel). I've seen this sort of problem in other scenarios where the remote reports threads in an unusual way -- in particular if the remote reports a different stopping thread for a 'step', you can see this crash. If you can still trigger this, the best thing is to start gdb and then "set debug remote 1" before triggering the problem. Then, send the entire log. --=20 You are receiving this mail because: You are on the CC list for the bug.=