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: igc: trying to chase a crash Date: Mon, 25 Nov 2024 21:23:23 +0200 Message-ID: <864j3vi0d0.fsf@gnu.org> References: <874j3v2lq3.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40930"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: =?utf-8?Q?=C3=93scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Nov 25 20:24:25 2024 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 1tFeh7-000AVZ-1z for ged-emacs-devel@m.gmane-mx.org; Mon, 25 Nov 2024 20:24:25 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tFegD-0003PL-LO; Mon, 25 Nov 2024 14:23:29 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tFegB-0003P4-4u for emacs-devel@gnu.org; Mon, 25 Nov 2024 14:23:27 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tFegA-0007cI-87; Mon, 25 Nov 2024 14:23:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=fPVsoN84yI0GiH+95XhOr1yleHpFMKfzXHdyoZH+RGU=; b=fqc3ujHNvL/6Qgq8VXV3 AorCarwi/uhHxsF3Doig13P0EhvdWeMYkwCyRM4sWr8mdNDqsxZShHujCXlis5ACw6i6/G+wDWqRt trVXrdC3+nwLBEqfiO2LayDrNdlxcOYHdz3zfW1lnLw9UbELjI+i0bP9jmGZR/tDUsP2ZGBRb6ulV i3HffC7XHKY+7jo8ahYJNnGzlN9fXDiRvlKRlAF3ZuiN5+76BQrxctkIAK/aey7iTsY/6bDXicBzJ QhUJSm6HxOaTrinexM7trQ6VfjczIoemuO64SgXd8smHaHgP/m5B7t2PPB58mYNSrMVTZ6UtmbKVW b5Dm55QX8SZqmQ==; In-Reply-To: <874j3v2lq3.fsf@telefonica.net> (message from =?utf-8?Q?=C3=93scar?= Fuentes on Mon, 25 Nov 2024 19:48:36 +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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:325699 Archived-At: > From: Óscar Fuentes > Date: Mon, 25 Nov 2024 19:48:36 +0100 > > I'm using scratch/igc on and off since some weeks for work (mostly > Dart/Flutter code edition with lsp-mode, quite stressing for the GC > system). Today it crashed, so I launched it again under gdb, and there > it SIGSEGVs consistently while processing the init files. That means > that it SIGSEGVs at the same point every time I try. SIGSEGV is used by MPS to implement memory barriers. The file src/.gdbinit on the branch has this: # Pass on signals used by MPS to suspend threads. if defined_HAVE_MPS # Print SIGSEGV for now, since it makes the logs more useful. Don't # stop, though. handle SIGSEGV nostop print pass handle SIGXFSZ nostop noprint pass handle SIGXCPU nostop noprint pass end So if you don't want to see these segfaults, change handle SIGSEGV nostop print pass to handle SIGSEGV nostop noprint pass > So I went to build it in debug mode to obtain a good backtrace, but the > build fails: > > ../../emacs/src/marker.c: In function ‘buf_bytepos_to_charpos’: > ../../emacs/src/marker.c:389:18: error: invalid operands to binary && (have ‘int’ and ‘Lisp_Object’) > 389 | if (record && BUF_MARKERS (b)) > | ~~~~~~ ^~ > | | > | int I tried to fix this now, please try again. > So right now here igc runs when executed from the shell, but crashes on > startup when executed from gdb. And builds succesfully in release mode, > but doesn't in debug mode. > > I wonder if either my build config is too infrequent or nobody is > testing igc lately? The segfaults you see are not real, they are arranged by MPS deliberately.