From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Odd gdb problem Date: Tue, 07 Dec 2021 14:48:02 +0200 Message-ID: <83r1aozim5.fsf@gnu.org> References: <87tufljz7t.fsf@gnus.org> <834k7l1p9u.fsf@gnu.org> <87lf0xjyl9.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34300"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 07 13:50:19 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1muZvH-0008ml-IB for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Dec 2021 13:50:19 +0100 Original-Received: from localhost ([::1]:55342 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1muZvG-0002tU-5X for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Dec 2021 07:50:18 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:42872) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muZt5-00016s-IN for emacs-devel@gnu.org; Tue, 07 Dec 2021 07:48:03 -0500 Original-Received: from [2001:470:142:3::e] (port=38062 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muZt5-0000kM-8E; Tue, 07 Dec 2021 07:48:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=lXRCzIwHsk7me32ry8KcK7BxT8/vCrYxFbsPr/HGbOM=; b=nYgLpSz+aoy9 a+3SpWe8+rryYfgSKwrZl9YSVMPay7YRaTLhE7GtnSQWw3G+/51EaRf9tKBlgG359eP8jb6EKAL4h xy5cZ3Ap5iZi6+oufnJZJOm/esGulKSW+gxGdhaT1sNsrcIVVazNhElzWT+T+QP9x6X059LREWj5y YgTQfMejNhLdkHHb7SRmpOQE0V4ZeH//9xo2G9JfMOIvTqfTYJvCUO3WtJ4DMc7pX2UEfC38XNTP6 ODHA1SK5ZQ5k7XgxROK4Nyiq2xAfa2zVCEG/uPw7t+2p1VePXhPVymuSFsWlc0xLwflwXgsc6PKfY NUJqiXsMVw9QmeRBViFfXA==; Original-Received: from [87.69.77.57] (port=2606 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muZt4-0004XA-O1; Tue, 07 Dec 2021 07:48:03 -0500 In-Reply-To: <87lf0xjyl9.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 06 Dec 2021 20:57:22 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:281237 Archived-At: > From: Lars Ingebrigtsen > Date: Mon, 06 Dec 2021 20:57:22 +0100 > Cc: emacs-devel@gnu.org > > Eli Zaretskii writes: > > > Is this with or without native-comp? > > Without any configure options. > > > Did you try rebuilding Emacs (i.e. delete temacs and bootstrap-emacs, > > and say "make")? > > Yup; did a "make extraclean" first. SIGTRAP is normally the signal generated when the program hits a breakpoint, so this is strange: it looks like GDB received a spurious SIGTRAP that it couldn't associate with one of its breakpoints. What does "info break" say inside GDB? One other idea I have is to say (gdb) handle SIGTRAP stop print pass and see what happens then. Maybe you will be able to see where does this SIGTRAP originate from.