From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E299A3858C60; Tue, 31 Oct 2023 17:20:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E299A3858C60 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1698772847; bh=cpbYtZpugD1Fj+DFCJQBsTnSU3VkeO0uCTxCdMDKw/A=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Xdzg0ea2ddmALynCQ4AkS4dQ09+RB3GVL9rpCG3Bs6AfKh/oMPQ1U60yxsCeWMy0v OnAJVLQxUgUd/puEmtmlcrvZlTRSo7ccn3ikrnHpVYrIf6TJnzzlsRT8yMNxLpDpPh mdRWdnuUSEz16FUsD8q9XoRbUn+LHEc4byS3t+nM= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: =?UTF-8?B?W0J1ZyBnZGIvMzEwMDhdIOKAnkxheW91dOKAnSBjcmFzaGVzIGdk?= =?UTF-8?B?YiAxMy4y?= Date: Tue, 31 Oct 2023 17:20:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 13.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical 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: 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=3D31008 --- Comment #6 from Tom Tromey --- (In reply to Zbigniew from comment #5) > Let me know step-by-step, what actually you want me to do. I would try 'gdb gdb', then produce the crash and then 'bt' to get a stack trace. However, this is only really useful if you have gdb debug info available. I don't know how to get that for your distro. --=20 You are receiving this mail because: You are on the CC list for the bug.=