From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6EDDA3858C2F; Tue, 24 Jan 2023 23:17:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6EDDA3858C2F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1674602227; bh=JFrwNi8cpfm0qDCkIukFbPB4IqMfyRZHtCIafHYrdvQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SC6TjJwd0zhzwHuE60Ox8kxqNEwPNJqY3H3cw56FxNSTdXOEZDePWdVEBOa2PKOeU EoXhXAMd/+U66jtLDP4UksnLdflfYTWMMmrrnNxYfnHftawZOwPjJksLlTP1DfHYTx gZD/QKq97FNKno7h9n7G+2Ssk0y3COQZNuQmbNk4= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug c++/30045] GDB crashes when command is used during layout Date: Tue, 24 Jan 2023 23:17:07 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tromey at sourceware dot org 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: 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=3D30045 --- Comment #3 from Tom Tromey --- In terminal A, run gdb and enter the TUI. In terminal B, run gdb but do not enter the TUI, just attach to the gdb in A. You can do this with 'attach PID', where the PID is the process ID of the first gdb. Then in terminal A, reproduce the crash. In B, type 'bt'. This should work ok if you have a gdb built with debug symbols. --=20 You are receiving this mail because: You are on the CC list for the bug.=