From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: MPS: Please check if scratch/igc builds with native compilation Date: Tue, 21 May 2024 14:46:30 -0400 Message-ID: References: <875xv76mkj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8608"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Gerd =?utf-8?Q?M=C3=B6llmann?= , Emacs Devel , Eli Zaretskii To: Helmut Eller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 21 20:47:43 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 1s9UWV-00024F-5Z for ged-emacs-devel@m.gmane-mx.org; Tue, 21 May 2024 20:47:43 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s9UVX-0003k5-7u; Tue, 21 May 2024 14:46:45 -0400 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 1s9UVL-0003ah-NA for emacs-devel@gnu.org; Tue, 21 May 2024 14:46:32 -0400 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 1s9UVL-0007ZL-Ey; Tue, 21 May 2024 14:46:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=hkmAN6f+Eq1s7m8K2X2Nwd8S8Oa7iupsXa31bGj/b3Q=; b=go2lXsmJQQZFNOEqeWUb mN7zT1ZLRpkyuNJYt7jGt5v/teLVEiP27HOSEHvoujV+ZWTXZTqVulsnpXWyZF6Ort6a6w8knmcxn tkJeowuRFMW95xzIhTItLtan9Z2OfklFvE3MFBwZsirRAyhnOg6T+1dtZ9w1t6AdlDVDJQmK6W2QK QrFAp8yNteQVeCHIkRA4ReGS5p7ZacrS0/zYADFujiCPwTGPr9RiCG0mNyFqI9zyhk5ba0mTiGv98 vafrdBHlWET07MrBUaZB1oRsLUVvM8FcYVhtN1JgBnZFiBtp8OWutT9dbyogDz6xdCmYcax8FrKaG bC/8BP4ft1zRJQ==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1s9UVK-0002XS-4O; Tue, 21 May 2024 14:46:30 -0400 In-Reply-To: <875xv76mkj.fsf@gmail.com> (Helmut Eller's message of "Tue, 21 May 2024 20:34:36 +0200") 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:319454 Archived-At: Helmut Eller writes: >> And if I run it under gdb I see we get a SIGSEGV in >> 'maybe_resize_hash_table' at fns.c:4987 >> >> memcpy (key, h->key, old_size * sizeof *key); > > Yes, this probably a memory barrier triggered by an allocation. In > gdb you need to say: signal SIGSEGV nostop print pass > so that it can continue. Or noprint, what you prefer. Thanks Helmut, (for the record if someone else see this, it was 'handle SIGSEGV nostop print pass') Anyway yes, to confirm that at least here looks reproducible. Andrea