From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 150D73858C27; Sun, 5 Nov 2023 16:09:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 150D73858C27 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1699200548; bh=ZXp+1FJbzGWNGdiJ6NA8imMV6dDp3IbCd6KcoNMB+/k=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hjFOUwp7VdIvclLa3vjLOHlLcrbO0Fh5tsCHQsRziWqr86cUXdLQai2VXmb//eIzs uD1wM06vA4Hi3vHW+E+kqhVo+hlmCPMr6qKO8lbYaY/cL4CzvG6nrQZYa2/PGIXiiG 8MIK2LhNAwppEjt39+a7YpML+3kR4J48fsih4138= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: =?UTF-8?B?W0J1ZyBnZGIvMzEwMDhdIOKAnkxheW91dOKAnSBjcmFzaGVzIGdk?= =?UTF-8?B?YiAxMy4y?= Date: Sun, 05 Nov 2023 16:09:07 +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 #11 from Tom Tromey --- (In reply to Zbigniew from comment #10) > OK, I recompiled and I did everything like before =E2=80=94 here's the ou= tput: > Thread 1 "gdb" received signal SIGSEGV, Segmentation fault. > 0x00007f81596fc318 in delwin () from /lib64/libncursesw.so.6 > (gdb) cont > Continuing. Right here you should invoke "bt" (rather than "cont") to get the stack tra= ce. Posting it here would be good. This crash occurs in delwin, in libncurses. This does not necessarily mean a curses bug. The next step would be to examine the output of=20 "bt" and look for the first frame that is in the gdb sources. You can go there with "frame 5" (e.g., if it is frame #5), then you can look at the local variables and whatnot. Normally in gdb this will be some destructor. --=20 You are receiving this mail because: You are on the CC list for the bug.=