From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.devel Subject: Re: 31.0.50; Emacs scratch/igc 6682d0e6c96 Crash on Linux, wayland Date: Wed, 04 Sep 2024 13:40:02 +0000 Message-ID: <87ed5z7d1v.fsf@protonmail.com> References: <87y148h7of.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22665"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, Helmut Eller To: Eval EXEC Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 04 16:08:36 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 1slqgW-0005hk-D6 for ged-emacs-devel@m.gmane-mx.org; Wed, 04 Sep 2024 16:08:36 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1slqg7-0000ym-Bz; Wed, 04 Sep 2024 10:08:11 -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 1slqF1-0007j6-Fy for emacs-devel@gnu.org; Wed, 04 Sep 2024 09:40:11 -0400 Original-Received: from mail-40131.protonmail.ch ([185.70.40.131]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1slqEz-0007bq-Ov for emacs-devel@gnu.org; Wed, 04 Sep 2024 09:40:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1725457206; x=1725716406; bh=0ckHJ1WJiZ02QtE0G5LGfkH9aQgH+NAFfOxDH1jnY+8=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=eUBfRI+VEWMeWlKmWBr4YxFIfhM8febCbOf/T76gg8nhXQj0zmRKKfItCUjwAZHRt RbrcRquRTsOYkjW0zXLJWFsPhl8EAQosg6lEwsNI2sXghBT8Zjmt6B7h0l+6xfG2Jg UeWcKgE2Yk76qS1FUV7RdkISE3X2Hua2GHI6hDkJQTRz5b0l8ukLFE7k4d4vHgyJ17 lRKM0I8KI4jotYiqDoV27BoslOCMGM48m4ZzVUmL3qHLE0gCJVwg/Hrp+hQC+ToXgM jMKEb3HznyqKtJKRKB0py04ZnCk4ChJz/PRUo3vOAU3EtSpkTq2GAy5pd9oVjxD4w0 8zfF9H4atYWyA== In-Reply-To: <87y148h7of.fsf@gmail.com> Feedback-ID: 112775352:user:proton X-Pm-Message-ID: 0086472dc7bcf0debeca120c8deb89c99039370d Received-SPF: pass client-ip=185.70.40.131; envelope-from=pipcet@protonmail.com; helo=mail-40131.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Wed, 04 Sep 2024 10:08:09 -0400 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:323358 Archived-At: "Eval EXEC" writes: > I'm help to test scratch/igc branch, and I have a crash When I editing > a rust file, M-x kill-process rust-analyzer, lsp-restart-workspace, > scrolling, and moving around the rust file buffer. > > Sorry, I don't know how to reproduce it. The backtrace is: > > ``` > (gdb) bt > #0 0x00000000006dfe09 in record_backtrace.lto_priv () > #1 0x00000000006e03df in deliver_profiler_signal () > #2 > #3 0x00000000007dea30 in sigHandle () > #4 That looks like the SIGPROF hit at a very bad time, after sigHandle was called but before it had time to lock the arena, which would have stopped the profiler handler from accessing memory. Helmut, do you have any ideas? Maybe we'll have to add SIGPROF to the SIGSEGV sa_mask after all and explicitly unblock it in the handler after setting a "just count this" flag? Pip