From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#75459: 31.0.50; scratch-igc: Breakpoint 1, terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=2147483647) at ./src/emacs.c:432 Date: Fri, 10 Jan 2025 14:46:40 +0000 Message-ID: <878qri3ewj.fsf@protonmail.com> References: <87zfk0p741.fsf@no.lan> <87frlst34b.fsf@no.lan> <87plkv3hzd.fsf@protonmail.com> <86msfz16na.fsf@gnu.org> <87ldvi3hok.fsf@protonmail.com> Reply-To: Pip Cet 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="8353"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , telegraph@gmx.net, 75459@debbugs.gnu.org To: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jan 10 15:47:29 2025 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1tWGIK-0001vy-Kk for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 10 Jan 2025 15:47:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tWGI6-00082t-Eg; Fri, 10 Jan 2025 09:47:15 -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 1tWGHv-00081X-QV for bug-gnu-emacs@gnu.org; Fri, 10 Jan 2025 09:47:03 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tWGHu-0000LW-7s for bug-gnu-emacs@gnu.org; Fri, 10 Jan 2025 09:47:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=MIME-Version:References:In-Reply-To:From:Date:To:Subject; bh=3df3JPra1FXOOYcAc4djq+9ZjyLWeUbq3Fl5qeFAvOc=; b=spflH3NsftlAFF/Y1g0VGcOcEoT88fdv2HLNup2WFBIWfg7Mv0N5yuEalSgLNFSpplOMucHm88gRqLl2F5Hm1CXmqzH+V2FsbN5YF6NSPwOGEssPei3/KjFAQfFnvGSaLgd4K/F/SyfSyrJIrgbbe+K+vQtaPtCxB4WuzxG1qPTjsBPnlVjQaee3ykf+pbMskf/+Ck3Q59l08cl693JNqRa7ek91KsXwwWIPrPSSIwuivDBhNhZ7D0dGw4d/mr11uVmq1dH3eMmoRhaZAQZG6Frhq34D48DELZmjyu/4yb8sAH/4oepY3xNFfoZg3Df2g9+/VbGGy07Dg7nyZRw8Qg==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tWGHu-0005lA-0M for bug-gnu-emacs@gnu.org; Fri, 10 Jan 2025 09:47:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Pip Cet Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 10 Jan 2025 14:47:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 75459 X-GNU-PR-Package: emacs Original-Received: via spool by 75459-submit@debbugs.gnu.org id=B75459.173652041222120 (code B ref 75459); Fri, 10 Jan 2025 14:47:01 +0000 Original-Received: (at 75459) by debbugs.gnu.org; 10 Jan 2025 14:46:52 +0000 Original-Received: from localhost ([127.0.0.1]:56886 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tWGHk-0005ki-7I for submit@debbugs.gnu.org; Fri, 10 Jan 2025 09:46:52 -0500 Original-Received: from mail-40131.protonmail.ch ([185.70.40.131]:33189) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1tWGHh-0005kU-Tr for 75459@debbugs.gnu.org; Fri, 10 Jan 2025 09:46:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1736520403; x=1736779603; bh=3df3JPra1FXOOYcAc4djq+9ZjyLWeUbq3Fl5qeFAvOc=; 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:List-Unsubscribe:List-Unsubscribe-Post; b=pXz3gHCgnFvDdYKH8E9HJSygmIKs+b6UPFpj72FwDoY6FUUIlGwkerHqqp5vwWlvE l+DNWh8Ve3gvIo1baMEitwhKjMq3CK8c0GcXZxy1C8YXXTfV9fG+hxYJ50FwBE4Qjv AkeMZnj7aUEXx3+bSxfveav8ZWWxo5UWbTf4xpOplC3aNzId9tctRM+bYpPmh9b87u e9Nv8J1gOFNEZK7fOpGtSh6FtnFkfNCRwTvavdFrPsvSx3qLIhwE6IDfwpMlA/BDuG bZiwO8cLYM1vgWMK3pbHk2bSj95PtXibgbGn0dmvq3XBMLh7GMwp/H4vloSMW5yTxd OwRhOj/mEyNgA== In-Reply-To: Feedback-ID: 112775352:user:proton X-Pm-Message-ID: 8f92ecb01d7152b08ada7abd4118a8432e4c5a2f X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:298891 Archived-At: Gerd M=C3=B6llmann writes: > Pip Cet writes: > >> Gerd M=C3=B6llmann writes: >> >>> Ah, that explains it, thanks! Didn't know about that hook. >> >> That explains why "backtrace" doesn't show up; it doesn't explain why >> backtrace_function asserts on data that we previously ensured would be o= f >> the right kind. > > True. > >>> I call that command manually when MPS gets in the way. Here is the >> >> Does lldb allow you to inspect memory that is behind a barrier? > > No, or at least I don't know how I could do that. It may have been unfair to call this a GDB bug: I don't know much about the ptrace API, and if the ptrace API allows modifying rodata and reading mprotected memory, there's a good chance that's a Linux kernel bug which isn't present in whatever macOS uses instead. Speaking of toolchain bugs, though, I appear to have "been" upgraded to a new GCC version which produces many new warnings, including what appears to me to be a false positive "null pointer dereference" (NOT a "potential null pointer dereference") in dispnew.c. (root_frame () can return a NULL pointer in some contexts, but not in this one, so this is, at best, a *potential* null pointer dereference, or a suggested additional assertion. A "null pointer dereference" without a "potential" is reserved for code paths which can be proven to dereference a null pointer, not for code paths which cannot be proven not to. So this is a GCC bug.) Still investigating the others, but: In file included from json.c:31: igc.h:88:7: warning: redundant redeclaration of =E2=80=98igc_xnmalloc_ambig= =E2=80=99 [-Wredundant-decls] 88 | void *igc_xnmalloc_ambig (ptrdiff_t nitems, ptrdiff_t item_size); | ^~~~~~~~~~~~~~~~~~ In file included from json.c:28: lisp.h:6117:14: note: previous declaration of =E2=80=98igc_xnmalloc_ambig= =E2=80=99 with type =E2=80=98void *(ptrdiff_t, ptrdiff_t)=E2=80=99 {aka = =E2=80=98void *(long int, long int)=E2=80=99} 6117 | extern void *igc_xnmalloc_ambig (ptrdiff_t nitems, ptrdiff_t item_s= ize); | ^~~~~~~~~~~~~~~~~~ igc.h:90:6: warning: redundant redeclaration of =E2=80=98igc_xfree=E2=80= =99 [-Wredundant-decls] 90 | void igc_xfree (void *p); | ^~~~~~~~~ lisp.h:6118:13: note: previous declaration of =E2=80=98igc_xfree=E2=80= =99 with type =E2=80=98void(void *)=E2=80=99 6118 | extern void igc_xfree (void *p); | ^~~~~~~~~ seems annoying, but avoidable. I'll push a "fix", but I wanted to explain why first: new useless GCC warnings force us to do that. Pip