From debbugs-submit-bounces@debbugs.gnu.org Mon Jan 20 18:32:32 2025 Received: (at submit) by debbugs.gnu.org; 20 Jan 2025 23:32:32 +0000 Received: from localhost ([127.0.0.1]:52121 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ta1Fv-000133-AR for submit@debbugs.gnu.org; Mon, 20 Jan 2025 18:32:32 -0500 Received: from lists.gnu.org ([2001:470:142::17]:51414) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ta1FE-00010P-6T for submit@debbugs.gnu.org; Mon, 20 Jan 2025 18:31:50 -0500 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 1tZzdy-0004Sn-6w for bug-gnu-emacs@gnu.org; Mon, 20 Jan 2025 16:49:14 -0500 Received: from mail.snapdragon.cc ([51.79.228.117]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tZzdv-0008AP-T9 for bug-gnu-emacs@gnu.org; Mon, 20 Jan 2025 16:49:13 -0500 From: Oliver Reiter DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snapdragon.cc; s=default; t=1737409748; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=+nOV24XVRhPllBmBv6b6WMd4hee11NZ3jFpAn9bR9+I=; b=DYcQgibdn/QcHZ/IybsVQB1W3Zj0PMpT6oMw87nAXEnoOqnCaBUHyQ2Y+hmuYP/i1jt8st HMCJFjN5Y2xtoS9ZbxEVhtwTBbgaFg32Dw4be8K3Q/M1wEAvWbmz6uTdZCZqsrZX5UFTO+ UPPt0FoAViHarE+D0JBR1OrQNAtjbVE= To: bug-gnu-emacs@gnu.org Subject: 31.0.50; feature/igc: crash report on Arch Linux, 2025-01-20 X-Debbugs-Cc: Date: Mon, 20 Jan 2025 22:49:02 +0100 Message-ID: <874j1t5f75.fsf@wiiw.ac.at> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=51.79.228.117; envelope-from=oliver.reiter@snapdragon.cc; helo=mail.snapdragon.cc 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, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: 0.9 (/) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.1 (/) Dear all, I opened emacs and started editing an .R file when I experienced this crash: Thread 1 "emacs" hit Breakpoint 1, terminate_due_to_signal (sig=6, backtrace_limit=40) at /home/reitero/build/sources/emacs/emacs/src/emacs.c:432 432 { (gdb) bt #0 terminate_due_to_signal (sig=6, backtrace_limit=40) at /home/reitero/build/sources/emacs/emacs/src/emacs.c:432 #1 0x00005555556d3525 in emacs_abort () at /home/reitero/build/sources/emacs/emacs/src/sysdep.c:2390 #2 0x000055555579f3a1 in fix_lisp_obj (ss=ss@entry=0x7fffffffbce8, pobj=pobj@entry=0x7fffaa0c5168) at /home/reitero/build/sources/emacs/emacs/src/igc.c:1099 #3 0x000055555579fc1b in fix_cons (ss=ss@entry=0x7fffffffbce8, cons=cons@entry=0x7fffaa0c5158) at /home/reitero/build/sources/emacs/emacs/src/igc.c:1889 #4 0x00005555557a1a38 in dflt_scan_obj (ss=ss@entry=0x7fffffffbce8, base_start=base_start@entry=0x7fffaa0c5158, base_limit=base_limit@entry=0x7fffaa0c5170, closure=closure@entry=0x0) at /home/reitero/build/sources/emacs/emacs/src/igc.c:1996 #5 0x00005555557a1c2f in dflt_scanx (ss=ss@entry=0x7fffffffbce8, base_start=, base_limit=0x7fffaa0c5170, closure=closure@entry=0x0) at /home/reitero/build/sources/emacs/emacs/src/igc.c:2088 #6 0x00005555557a1c6b in dflt_scan (ss=0x7fffffffbce8, base_start=, base_limit=) at /home/reitero/build/sources/emacs/emacs/src/igc.c:2099 #7 0x0000555555835165 in amcSegScan () #8 0x0000555555864340 in traceScanSegRes () #9 0x000055555586452a in traceScanSeg () #10 0x0000555555865386 in TraceAdvance () #11 0x0000555555865b4d in TracePoll () #12 0x0000555555865db9 in ArenaPoll () #13 0x00005555558661a3 in mps_ap_fill () #14 0x00005555557a0cd7 in alloc_impl (size=size@entry=24, type=type@entry=IGC_OBJ_CONS, ap=0x7fffe8001980) at /home/reitero/build/sources/emacs/emacs/src/igc.c:3976 #15 0x00005555557a0dc6 in alloc (size=size@entry=24, type=type@entry=IGC_OBJ_CONS) at /home/reitero/build/sources/emacs/emacs/src/igc.c:4004 #16 0x00005555557a0de7 in igc_make_cons (car=0x2aaa69da0e30, cdr=0x7fffa992e6bb) at /home/reitero/build/sources/emacs/emacs/src/igc.c:4033 #17 0x000055555570df6c in Fcons (car=, cdr=) at /home/reitero/build/sources/emacs/emacs/src/alloc.c:2870 #18 0x000055555572f7a3 in funcall_subr (subr=subr@entry=0x7fffbeac8998, numargs=numargs@entry=1, args=args@entry=0x7fffffffc208) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3183 #19 0x000055555572dfcb in funcall_general (fun=0x7fffbeac899d, numargs=numargs@entry=1, args=args@entry=0x7fffffffc208) at /home/reitero/build/sources/emacs/emacs/src/lisp.h:2335 #20 0x000055555572e0e3 in Ffuncall (nargs=2, args=0x7fffffffc200) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3115 #21 0x00005555557346b3 in mapcar1 (leni=leni@entry=15, vals=vals@entry=0x7fffffffc260, fn=fn@entry=0x7fffbeac899d, seq=seq@entry=0x7fffb5c82e4b) at /home/reitero/build/sources/emacs/emacs/src/fns.c:3391 #22 0x0000555555738493 in Fmapcar (function=0x7fffbeac899d, sequence=0x7fffb5c82e4b) at /home/reitero/build/sources/emacs/emacs/src/fns.c:3511 #23 0x00007fffc7f84458 in F6576696c2d6d6f64652d666f722d6b65796d6170_evil_mode_for_keymap_0 () from /home/reitero/.config/emacs/.local.igc/cache/eln/31.0.50-d8b03b85/evil-core-b0b3fed6-7d34b371.eln #24 0x000055555572f7b7 in funcall_subr (subr=subr@entry=0x7fffaea82480, numargs=numargs@entry=2, args=args@entry=0x7fffffffc4f8) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3185 #25 0x000055555572dfcb in funcall_general (fun=0x7fffaea82485, numargs=numargs@entry=2, args=args@entry=0x7fffffffc4f8) at /home/reitero/build/sources/emacs/emacs/src/lisp.h:2335 #26 0x000055555572e0e3 in Ffuncall (nargs=3, args=0x7fffffffc4f0) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3115 #27 0x00007fffc7f84794 in F6576696c2d73746174652d617578696c696172792d6b65796d617073_evil_state_auxiliary_keymaps_0 () from /home/reitero/.config/emacs/.local.igc/cache/eln/31.0.50-d8b03b85/evil-core-b0b3fed6-7d34b371.eln #28 0x000055555572f7a3 in funcall_subr (subr=subr@entry=0x7fffaea821d8, numargs=numargs@entry=1, args=args@entry=0x7fffffffc6d8) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3183 #29 0x000055555572dfcb in funcall_general (fun=0x7fffaea821dd, numargs=numargs@entry=1, args=args@entry=0x7fffffffc6d8) at /home/reitero/build/sources/emacs/emacs/src/lisp.h:2335 #30 0x000055555572e0e3 in Ffuncall (nargs=2, args=0x7fffffffc6d0) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3115 #31 0x00007fffc7f83812 in F6576696c2d73746174652d6b65796d617073_evil_state_keymaps_0 () from /home/reitero/.config/emacs/.local.igc/cache/eln/31.0.50-d8b03b85/evil-core-b0b3fed6-7d34b371.eln #32 0x000055555572f8a2 in funcall_subr (subr=subr@entry=0x7fffaea82590, numargs=numargs@entry=2, args=args@entry=0x7fffffffcbb8) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3206 #33 0x000055555572dfcb in funcall_general (fun=0x7fffaea82595, numargs=numargs@entry=2, args=args@entry=0x7fffffffcbb8) at /home/reitero/build/sources/emacs/emacs/src/lisp.h:2335 #34 0x000055555572e0e3 in Ffuncall (nargs=nargs@entry=3, args=args@entry=0x7fffffffcbb0) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3115 #35 0x000055555572fc7b in Fapply (nargs=3, args=0x7fffffffcbb0) at /home/reitero/build/sources/emacs/emacs/src/eval.c:2744 #36 0x00007fffc7f83b10 in F6576696c2d73746174652d6b65796d617073_evil_state_keymaps_0 () from /home/reitero/.config/emacs/.local.igc/cache/eln/31.0.50-d8b03b85/evil-core-b0b3fed6-7d34b371.eln #37 0x000055555572f8a2 in funcall_subr (subr=subr@entry=0x7fffaea82590, numargs=numargs@entry=1, args=args@entry=0x7fffffffcdd8) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3206 #38 0x000055555572dfcb in funcall_general (fun=0x7fffaea82595, numargs=numargs@entry=1, args=args@entry=0x7fffffffcdd8) at /home/reitero/build/sources/emacs/emacs/src/lisp.h:2335 #39 0x000055555572e0e3 in Ffuncall (nargs=2, args=0x7fffffffcdd0) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3115 #40 0x00007fffc7f83ddf in F6576696c2d6e6f726d616c697a652d6b65796d617073_evil_normalize_keymaps_0 () from /home/reitero/.config/emacs/.local.igc/cache/eln/31.0.50-d8b03b85/evil-core-b0b3fed6-7d34b371.eln #41 0x000055555572f7a3 in funcall_subr (subr=subr@entry=0x7fffaea82e80, numargs=numargs@entry=0, args=args@entry=0x7fffffffd018) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3183 #42 0x000055555572dfcb in funcall_general (fun=0x7fffaea82e85, numargs=numargs@entry=0, args=args@entry=0x7fffffffd018) at /home/reitero/build/sources/emacs/emacs/src/lisp.h:2335 #43 0x000055555572e0e3 in Ffuncall (nargs=1, args=0x7fffffffd010) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3115 #44 0x00007fffc7f5e898 in F6576696c2d6e6f726d616c2d7374617465_evil_normal_state_0 () from /home/reitero/.config/emacs/.local.igc/cache/eln/31.0.50-d8b03b85/evil-states-2dd1009e-c78caef2.eln #45 0x000055555572f7a3 in funcall_subr (subr=subr@entry=0x7fffaea6a948, numargs=numargs@entry=0, args=args@entry=0x7fffffffd4f0) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3183 #46 0x000055555572dfcb in funcall_general (fun=0x7fffaea6a94d, numargs=numargs@entry=0, args=args@entry=0x7fffffffd4f0) at /home/reitero/build/sources/emacs/emacs/src/lisp.h:2335 #47 0x000055555572e0e3 in Ffuncall (nargs=1, args=0x7fffffffd4e8) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3115 #48 0x0000555555728f38 in Ffuncall_interactively (nargs=1, args=0x7fffffffd4e8) at /home/reitero/build/sources/emacs/emacs/src/callint.c:250 #49 0x000055555572f8a2 in funcall_subr (subr=subr@entry=0x555555e195a0 , numargs=numargs@entry=1, args=args@entry=0x7fffffffd4e8) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3206 #50 0x000055555572dfcb in funcall_general (fun=0x555555e195a5 , numargs=numargs@entry=1, args=args@entry=0x7fffffffd4e8) at /home/reitero/build/sources/emacs/emacs/src/lisp.h:2335 #51 0x000055555572e0e3 in Ffuncall (nargs=nargs@entry=2, args=args@entry=0x7fffffffd4e0) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3115 #52 0x000055555572fc5d in Fapply (nargs=3, args=0x7fffffffd4e0) at /home/reitero/build/sources/emacs/emacs/src/eval.c:2740 #53 0x00005555557292e2 in Fcall_interactively (function=0x2aaa68ca21b8, record_flag=0x0, keys=0x7fffa96e231d) at /home/reitero/build/sources/emacs/emacs/src/callint.c:342 #54 0x00007fffe0000925 in F636f6d6d616e642d65786563757465_command_execute_0 () from /home/reitero/build/sources/emacs/emacs/src/../native-lisp/31.0.50-d8b03b85/preloaded/simple-fab5b0cf-eda3ce07.eln #55 0x000055555572f7eb in funcall_subr (subr=subr@entry=0x7fffeb814a38, numargs=numargs@entry=1, args=args@entry=0x7fffffffd758) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3189 #56 0x000055555572dfcb in funcall_general (fun=0x7fffeb814a3d, numargs=numargs@entry=1, args=args@entry=0x7fffffffd758) at /home/reitero/build/sources/emacs/emacs/src/lisp.h:2335 #57 0x000055555572e0e3 in Ffuncall (nargs=2, args=0x7fffffffd750) at /home/reitero/build/sources/emacs/emacs/src/eval.c:3115 #58 0x00005555556b7ce2 in command_loop_1 () at /home/reitero/build/sources/emacs/emacs/src/keyboard.c:1556 #59 0x000055555572c919 in internal_condition_case (bfun=0x5555556b77e1 , handlers=, hfun=0x5555556b486c ) at /home/reitero/build/sources/emacs/emacs/src/eval.c:1627 #60 0x00005555556b4a97 in command_loop_2 (handlers=handlers@entry=0xa8) at /home/reitero/build/sources/emacs/emacs/src/keyboard.c:1174 #61 0x000055555572c857 in internal_catch (tag=, func=0x5555556b4a75 , arg=0xa8) at /home/reitero/build/sources/emacs/emacs/src/eval.c:1306 #62 0x00005555556b5c77 in command_loop () at /home/reitero/build/sources/emacs/emacs/src/keyboard.c:1152 #63 0x00005555556b5d0e in recursive_edit_1 () at /home/reitero/build/sources/emacs/emacs/src/keyboard.c:760 #64 0x00005555556b5eac in Frecursive_edit () at /home/reitero/build/sources/emacs/emacs/src/keyboard.c:843 #65 0x00005555556b7316 in main (argc=, argv=0x7fffffffdb68) at /home/reitero/build/sources/emacs/emacs/src/emacs.c:2658 Lisp Backtrace: 0xbeac8998 PVEC_SUBR "evil-mode-for-keymap" (0xffffc4f8) "evil-state-auxiliary-keymaps" (0xffffc6d8) "evil-state-keymaps" (0xffffcbb8) "evil-state-keymaps" (0xffffcdd8) "evil-normalize-keymaps" (0xffffd018) "evil-normal-state" (0xffffd4f0) "funcall-interactively" (0xffffd4e8) "command-execute" (0xffffd758) In GNU Emacs 31.0.50 (build 4, x86_64-pc-linux-gnu, GTK+ Version 3.24.43, cairo version 1.18.2) of 2025-01-20 built on wilap Repository revision: 35437854166f8d0c1deceb7aba50f27cc838b490 Repository branch: feature/igc System Description: Arch Linux Configured using: 'configure 'CFLAGS=-g3 -ggdb -Og -fno-omit-frame-pointer' CPPFLAGS=-I/home/reitero/.local/lib/mps LDFLAGS=-L/home/reitero/.local/lib/mps --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib --localstatedir=/var --with-mps=yes --with-gameuser=root:games --with-pgtk --with-xft --with-harfbuzz --with-modules --without-compress-install --without-m17n-flt --with-libotf --without-imagemagick --without-gsettings --without-gconf --with-native-compilation=aot --with-tree-sitter --enable-link-time-optimization' Configured features: ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM HARFBUZZ JPEG LCMS2 LIBOTF LIBSYSTEMD LIBXML2 MODULES MPS NATIVE_COMP NOTIFY INOTIFY PDUMPER PGTK PNG RSVG SECCOMP SOUND SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS TREE_SITTER WEBP XIM GTK3 ZLIB Important settings: value of $LANG: de_AT.UTF-8 locale-coding-system: utf-8-unix From debbugs-submit-bounces@debbugs.gnu.org Wed Jan 22 05:35:22 2025 Received: (at 75710) by debbugs.gnu.org; 22 Jan 2025 10:35:22 +0000 Received: from localhost ([127.0.0.1]:60080 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1taY4w-0003MU-77 for submit@debbugs.gnu.org; Wed, 22 Jan 2025 05:35:22 -0500 Received: from mail-40134.protonmail.ch ([185.70.40.134]:58781) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1taY4t-0003MC-7f for 75710@debbugs.gnu.org; Wed, 22 Jan 2025 05:35:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1737542112; x=1737801312; bh=DuDQIhUVWzQGpVk/3Vr1oXW9yIyC4AssSIgwWRb3WNs=; 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=pcg3I8ChDK3Clrr7Iw+DdeTZFOW4c+3GD6EXD+ubSRd2x+2/PAwx3+YHwKrHlcpS8 rqHzXv5a5SReZQvpz/k/6HlIg0vuj/kyBTDU3dMZ4jrhIpwi6htJWzdlBHdp7YUYCP /czpLlQ3lmiUWONrjE7UHYf254XGWpnVfzxHVAMORHtf40HHDMOnycbpu0rQN3PQOX Pl8ldj4pBns23DVyxLFeYOKMiJ6BaOjHIwH73jvZr7uSP9RxAl1HRY2GjT9GcD8zo8 g0Z2qh2CrFgUupV7NgpXjdfdKSnHf8Mgp4zs7bt+TyvVLX0id++t0ZX/grVKvv29BF Ftu93NwNmzoPw== Date: Wed, 22 Jan 2025 10:35:09 +0000 To: 75710@debbugs.gnu.org From: Pip Cet Subject: Re: bug#75710: 31.0.50; feature/igc: crash report on Arch Linux, 2025-01-20 Message-ID: <87jzandtm3.fsf@protonmail.com> In-Reply-To: <874j1t5f75.fsf@wiiw.ac.at> References: <874j1t5f75.fsf@wiiw.ac.at> Feedback-ID: 112775352:user:proton X-Pm-Message-ID: 43c6a960a2fb59b797b068700f0f877cf3f837f7 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 75710 Cc: Oliver Reiter X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) "Oliver Reiter via \"Bug reports for GNU Emacs, the Swiss army knife of tex= t editors\"" writes: > Dear all, > > I opened emacs and started editing an .R file when I experienced this > crash: Thanks for the report! While we would like to investigate this further if you can access the GDB data, there is a possible, but unlikely, explanation in bug#75754. Can you confirm whether you have access to the GDB session? I would recommend generating a coredump file using "gcore" and saving it along with the emacs executable and emacs.pdmp file so we can investigate this further. The reason I consider the explanation unlikely is that the styled_format bug would most likely result in strings being moved by the GC, but this crash happened while scanning a cons cell. It's still possible: we'll have to investigate whether the elisp you ran might have been a heavy user of styled_format. Can you please let me know which commit is in use by this build? Thanks! Pip From debbugs-submit-bounces@debbugs.gnu.org Wed Jan 22 06:49:23 2025 Received: (at 75710) by debbugs.gnu.org; 22 Jan 2025 11:49:23 +0000 Received: from localhost ([127.0.0.1]:60353 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1taZEY-00075l-Js for submit@debbugs.gnu.org; Wed, 22 Jan 2025 06:49:23 -0500 Received: from mail.snapdragon.cc ([2402:1f00:8001:f75::2]:58334) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1taZEV-00075S-8M for 75710@debbugs.gnu.org; Wed, 22 Jan 2025 06:49:20 -0500 From: Oliver Reiter DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snapdragon.cc; s=default; t=1737546554; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=JnTGsz4iwwFRaBh1U8NKVAeWAqCfNWD6m7BangycBTs=; b=ga//1n1T8J0eJrHPvcMLoyF1F9kD2zWKt6LV5rO2p2Ep5FlFM4Ny+CO6JfLQm8CcEQqidk 6guvp721/kegeBKzMP+dA5aMWy+iKE4nIBPehw2Bp5QaqcBK66X4keRN4Y9dOhu8LhXSbo hLR0ot25PqHV/7nPH4nTLvMlk0Nzrbw= To: Pip Cet Subject: Re: bug#75710: 31.0.50; feature/igc: crash report on Arch Linux, 2025-01-20 In-Reply-To: <87jzandtm3.fsf@protonmail.com> (Pip Cet's message of "Wed, 22 Jan 2025 10:35:09 +0000") References: <874j1t5f75.fsf@wiiw.ac.at> <87jzandtm3.fsf@protonmail.com> Date: Wed, 22 Jan 2025 12:49:11 +0100 Message-ID: <87sepbqdag.fsf@snapdragon.cc> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 75710 Cc: 75710@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --=-=-= Content-Type: text/plain Content-Disposition: inline Pip Cet writes: > "Oliver Reiter via \"Bug reports for GNU Emacs, the Swiss army knife of text editors\"" writes: > >> Dear all, >> >> I opened emacs and started editing an .R file when I experienced this >> crash: > > Thanks for the report! While we would like to investigate this further > if you can access the GDB data, there is a possible, but unlikely, > explanation in bug#75754. > > Can you confirm whether you have access to the GDB session? I would > recommend generating a coredump file using "gcore" and saving it along > with the emacs executable and emacs.pdmp file so we can investigate this > further. I do have the coredump and haven't rebuild emacs yet. > The reason I consider the explanation unlikely is that the styled_format > bug would most likely result in strings being moved by the GC, but this > crash happened while scanning a cons cell. It's still possible: we'll > have to investigate whether the elisp you ran might have been a heavy > user of styled_format. > > Can you please let me know which commit is in use by this build? Its commit 35437854166f8d0c1deceb7aba50f27cc838b490 (HEAD -> feature/igc, origin/feature/igc) Author: Stefan Kangas Date: Mon Jan 20 03:33:29 2025 +0100 Avoid case_Lisp_Int macro in igc.c > > Thanks! > > Pip Happy to help, Oliver --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Wed Jan 22 07:56:46 2025 Received: (at 75710) by debbugs.gnu.org; 22 Jan 2025 12:56:47 +0000 Received: from localhost ([127.0.0.1]:60800 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1taaHm-0008JF-BX for submit@debbugs.gnu.org; Wed, 22 Jan 2025 07:56:46 -0500 Received: from mail-40133.protonmail.ch ([185.70.40.133]:60891) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1taaHj-0008It-2q for 75710@debbugs.gnu.org; Wed, 22 Jan 2025 07:56:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1737550595; x=1737809795; bh=gUcsWanFZmA2dGIXwTXJMEHlvBI18jtMK3In3hh06bc=; 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=eci1LELYUVPlPHugFZ1KrJzRGRBt2sQepzHU3Gx6Z4fs924/Cpe7JMxxwBvzvf7AI Hs9El4pZUOLbvsrlytL1ipw0OcoSURsLiJBpX3zvBvkuPp13kuFe+u7j5EdP4XBYpZ oOdztJL0MWsezaxT0qnLxUrsWtwPiVlDseQLUYL0tHCtvYwEz+//wGJwth+P9WHKkD 6C7ZJ3HNi57R6gfvcx6UNe3wdsVA48OZAMZ3rzcVUyaxg/irRUjt1hOeAsb5P7su5W M06jCBF5saUD54bz1SxmHRvKvYZMlpMxkEqOp6XgwPIgotHx7PSrjpfMPYc7dhnSM9 4EExc8DImpFJg== Date: Wed, 22 Jan 2025 12:56:31 +0000 To: 75710@debbugs.gnu.org From: Pip Cet Subject: Re: bug#75710: 31.0.50; feature/igc: crash report on Arch Linux, 2025-01-20 Message-ID: <87o6zzc8i1.fsf@protonmail.com> In-Reply-To: <874j1t5f75.fsf@wiiw.ac.at> References: <874j1t5f75.fsf@wiiw.ac.at> Feedback-ID: 112775352:user:proton X-Pm-Message-ID: 7b778159927ec3df7ee718d75dec1a8ba17f522e MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 75710 Cc: Oliver Reiter X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) "Oliver Reiter via \"Bug reports for GNU Emacs, the Swiss army knife of tex= t editors\"" writes: > Dear all, > > I opened emacs and started editing an .R file when I experienced this > crash: Responding to this again now I've had time to look at the backtrace: > Thread 1 "emacs" hit Breakpoint 1, terminate_due_to_signal (sig=3D6, back= trace_limit=3D40) at /home/reitero/build/sources/emacs/emacs/src/emacs.c:43= 2 > 432=09{ > (gdb) bt > #0 terminate_due_to_signal (sig=3D6, backtrace_limit=3D40) at /home/reit= ero/build/sources/emacs/emacs/src/emacs.c:432 > #1 0x00005555556d3525 in emacs_abort () at /home/reitero/build/sources/e= macs/emacs/src/sysdep.c:2390 > #2 0x000055555579f3a1 in fix_lisp_obj (ss=3Dss@entry=3D0x7fffffffbce8, p= obj=3Dpobj@entry=3D0x7fffaa0c5168) at /home/reitero/build/sources/emacs/ema= cs/src/igc.c:1099 > #3 0x000055555579fc1b in fix_cons (ss=3Dss@entry=3D0x7fffffffbce8, cons= =3Dcons@entry=3D0x7fffaa0c5158) at /home/reitero/build/sources/emacs/emacs/= src/igc.c:1889 > #4 0x00005555557a1a38 in dflt_scan_obj (ss=3Dss@entry=3D0x7fffffffbce8, = base_start=3Dbase_start@entry=3D0x7fffaa0c5158, base_limit=3Dbase_limit@ent= ry=3D0x7fffaa0c5170, closure=3Dclosure@entry=3D0x0) > at /home/reitero/build/sources/emacs/emacs/src/igc.c:1996 > #5 0x00005555557a1c2f in dflt_scanx (ss=3Dss@entry=3D0x7fffffffbce8, bas= e_start=3D, base_limit=3D0x7fffaa0c5170, closure=3Dclosure@e= ntry=3D0x0) at /home/reitero/build/sources/emacs/emacs/src/igc.c:2088 > #6 0x00005555557a1c6b in dflt_scan (ss=3D0x7fffffffbce8, base_start=3D, base_limit=3D) at /home/reitero/build/sources= /emacs/emacs/src/igc.c:2099 I originally thought this indicated that a cons cell must have moved. Upon reflection, that's not necessarily likely: we scanned a cons whose cdr contained nonsensical data that should never have been in a cons cell; so something overwrote what MPS thought of a cons cell, and probably some memory before and after it, and we might have been in a middle of a segment and the previous object scanned by pure luck (or the corruption might have started at the header word). > Lisp Backtrace: > 0xbeac8998 PVEC_SUBR > "evil-mode-for-keymap" (0xffffc4f8) > "evil-state-auxiliary-keymaps" (0xffffc6d8) > "evil-state-keymaps" (0xffffcbb8) > "evil-state-keymaps" (0xffffcdd8) > "evil-normalize-keymaps" (0xffffd018) > "evil-normal-state" (0xffffd4f0) > "funcall-interactively" (0xffffd4e8) > "command-execute" (0xffffd758) I looked at evil-mode (hopefully, what I'm about to say applies to the precise version you're running, too): it appears to use Fformat quite a bit: I loaded and started it, and it was called 845 times in that Emacs session. Many of the calls had more than 2 arguments, which is, I believe, most likely required for the bug to be realistic. While unsatisfying, my very preliminary conclusion is that there is a significant chance that this is bug#75754. My plan is to fix this bug unconditionally (without #ifdef HAVE_MPS) on feature/igc because I believe the bug is present, albeit much less likely, on master, and the ultimate fix for bug#75754 is likely to be both very different and take some time. Objections to this? > In GNU Emacs 31.0.50 (build 4, x86_64-pc-linux-gnu, GTK+ Version > 3.24.43, cairo version 1.18.2) of 2025-01-20 built on wilap > Repository revision: 35437854166f8d0c1deceb7aba50f27cc838b490 > Repository branch: feature/igc > System Description: Arch Linux > > Configured using: > 'configure 'CFLAGS=3D-g3 -ggdb -Og -fno-omit-frame-pointer' ^^^ I confess I rarely build with -Og: I'm in the -O0 team, or -Os just to see some different compiler warnings once in a while. Thanks for testing with this flag; it might mean you see bugs others don't. In particular, stack marking with -O0 behaves in a more obvious fashion than in optimized builds; while the intention of -Og is to keep variables in the right location for debugging, I don't know how good GCC is at doing that in practice. Pip From debbugs-submit-bounces@debbugs.gnu.org Wed Jan 22 08:12:16 2025 Received: (at 75710) by debbugs.gnu.org; 22 Jan 2025 13:12:16 +0000 Received: from localhost ([127.0.0.1]:60848 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1taaWl-0000gU-FL for submit@debbugs.gnu.org; Wed, 22 Jan 2025 08:12:15 -0500 Received: from mail.snapdragon.cc ([51.79.228.117]:45972) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1taaWh-0000gF-8z for 75710@debbugs.gnu.org; Wed, 22 Jan 2025 08:12:12 -0500 From: Oliver Reiter DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snapdragon.cc; s=default; t=1737551527; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=RE+Kqt3RrxysuPT0CS32TNYS3kDsgqyfmToxq6pKSDA=; b=Hl0duEVQkprs8a3mZOJwc95L8vCY2l83/jN7I7cJSVLTyQKIRcEvaMe6urBrAuAGUB6kHS kiqZjLQaWZUCL3a09JZp5rGJO4dNrH0stRsg+cFYCL6tOsQBSARWG/fbfeVHh1mIyYYFiS 00Q18LWjqstVNRKaT7YKwNFxg4vMAuE= To: Pip Cet Subject: Re: bug#75710: 31.0.50; feature/igc: crash report on Arch Linux, 2025-01-20 In-Reply-To: <87o6zzc8i1.fsf@protonmail.com> (Pip Cet's message of "Wed, 22 Jan 2025 12:56:31 +0000") References: <874j1t5f75.fsf@wiiw.ac.at> <87o6zzc8i1.fsf@protonmail.com> Date: Wed, 22 Jan 2025 14:12:02 +0100 Message-ID: <87ikq7q9gd.fsf@snapdragon.cc> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 75710 Cc: 75710@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --=-=-= Content-Type: text/plain Content-Disposition: inline Pip Cet writes: > While unsatisfying, my very preliminary conclusion is that there is a > significant chance that this is bug#75754. My plan is to fix this bug > unconditionally (without #ifdef HAVE_MPS) on feature/igc because I > believe the bug is present, albeit much less likely, on master, and the > ultimate fix for bug#75754 is likely to be both very different and take > some time. > > Objections to this? If you are asking me: no objections. >> In GNU Emacs 31.0.50 (build 4, x86_64-pc-linux-gnu, GTK+ Version >> 3.24.43, cairo version 1.18.2) of 2025-01-20 built on wilap >> Repository revision: 35437854166f8d0c1deceb7aba50f27cc838b490 >> Repository branch: feature/igc >> System Description: Arch Linux >> >> Configured using: >> 'configure 'CFLAGS=-g3 -ggdb -Og -fno-omit-frame-pointer' > ^^^ > > I confess I rarely build with -Og: I'm in the -O0 team, or -Os just to > see some different compiler warnings once in a while. Thanks for > testing with this flag; it might mean you see bugs others don't. > > In particular, stack marking with -O0 behaves in a more obvious fashion > than in optimized builds; while the intention of -Og is to keep > variables in the right location for debugging, I don't know how good GCC > is at doing that in practice. Thanks for the insight, I'll build with -O0 next time. --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Wed Jan 22 16:10:14 2025 Received: (at 75710) by debbugs.gnu.org; 22 Jan 2025 21:10:14 +0000 Received: from localhost ([127.0.0.1]:36843 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tahzJ-00016z-KG for submit@debbugs.gnu.org; Wed, 22 Jan 2025 16:10:13 -0500 Received: from mail-40133.protonmail.ch ([185.70.40.133]:37461) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1tahzG-00011G-FC for 75710@debbugs.gnu.org; Wed, 22 Jan 2025 16:10:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1737580203; x=1737839403; bh=9kVucXYCaUpapPdThTLAgGbJYNKU2aW1G+qcoh2eCUg=; 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=VjFv/hXGjHzbwiwLYGDZ4CfUO4ru24FwDK2qvVNNsi+3H3eAM8LLSKCbaYn1pWE+g +AtpwMbuGqENHmKigUhsrAqdboijbftzrIyWME/FdKd83GdGM9Ebavwshs0oK03icI GerxrNVl8HN4H2Ti9szc26BLo61Y1MryfbhQVi5hEWrQ92vvMLkOttUmG7BOFTCfaI Y12tCdcv/oIP8zHFqIS5BRZG5qhbXv6PZ/3lOUXEloaC8BgFj3orivwkqZH4V5m1y5 kTIj4xNpGE9T4sxRxq37FWQiXga1rLFHBUzB5XBPL7XQl6sWTYdWtwZZHVxoq9/1jY 0/1EFYyT5T2wg== Date: Wed, 22 Jan 2025 21:09:58 +0000 To: Oliver Reiter From: Pip Cet Subject: Re: bug#75710: 31.0.50; feature/igc: crash report on Arch Linux, 2025-01-20 Message-ID: <87v7u67dyb.fsf@protonmail.com> In-Reply-To: <87ikq7q9gd.fsf@snapdragon.cc> References: <874j1t5f75.fsf@wiiw.ac.at> <87o6zzc8i1.fsf@protonmail.com> <87ikq7q9gd.fsf@snapdragon.cc> Feedback-ID: 112775352:user:proton X-Pm-Message-ID: 898fd301bb38e30449ce1254a4dd226f19e86233 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 75710 Cc: 75710@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) "Oliver Reiter" writes: > Pip Cet writes: > >> While unsatisfying, my very preliminary conclusion is that there is a >> significant chance that this is bug#75754. My plan is to fix this bug >> unconditionally (without #ifdef HAVE_MPS) on feature/igc because I >> believe the bug is present, albeit much less likely, on master, and the >> ultimate fix for bug#75754 is likely to be both very different and take >> some time. >> >> Objections to this? > > If you are asking me: no objections. A preliminary workaround for bug#75754 has been installed on feature/igc, erring on the side of protecting too many objects rather than too few of them. I would ask you to please try the current branch, and to report any further crashes you may see as a new bug; I may be wrong about all your crashes being due to this bug, but maybe I'm right about one of them :-) Thanks for the reports, again! If you don't see a crash, can you let us know (without a new bug, ideally) in a few days, and then we can mark these as probably closed? Thanks! >>> In GNU Emacs 31.0.50 (build 4, x86_64-pc-linux-gnu, GTK+ Version >>> 3.24.43, cairo version 1.18.2) of 2025-01-20 built on wilap >>> Repository revision: 35437854166f8d0c1deceb7aba50f27cc838b490 >>> Repository branch: feature/igc >>> System Description: Arch Linux >>> >>> Configured using: >>> 'configure 'CFLAGS=3D-g3 -ggdb -Og -fno-omit-frame-pointer' >> ^^^ >> >> I confess I rarely build with -Og: I'm in the -O0 team, or -Os just to >> see some different compiler warnings once in a while. Thanks for >> testing with this flag; it might mean you see bugs others don't. >> >> In particular, stack marking with -O0 behaves in a more obvious fashion >> than in optimized builds; while the intention of -Og is to keep >> variables in the right location for debugging, I don't know how good GCC >> is at doing that in practice. > > Thanks for the insight, I'll build with -O0 next time. I wasn't trying to get you to do that. Not going to stop you either, of course. All options need to be tested; we just need to find the right balance between expanding our tests to find all possible crashes and gathering data on the stability and usability of IGC by running a few common builds and hoping they don't crash all the time. Pip From debbugs-submit-bounces@debbugs.gnu.org Wed Jan 22 16:33:04 2025 Received: (at 75710) by debbugs.gnu.org; 22 Jan 2025 21:33:05 +0000 Received: from localhost ([127.0.0.1]:36884 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1taiLQ-0002Gw-Dp for submit@debbugs.gnu.org; Wed, 22 Jan 2025 16:33:04 -0500 Received: from mail.snapdragon.cc ([51.79.228.117]:38974) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1taiLL-0002GD-QR for 75710@debbugs.gnu.org; Wed, 22 Jan 2025 16:33:03 -0500 From: Oliver Reiter DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snapdragon.cc; s=default; t=1737581575; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=R3Z45Xll4NqjIB8EaK60kR6mzOaB/Pwpu4vzLagnG0s=; b=XsXQ4UwyWhD4xWBny8awwiybRqFKTP/K22P7dKXpVEUfyyiVtvqcWFEvJgfbCVsKCvrckP gHSocqwsSJVXDDvM6poPFZKmomzNuknGL3cZhkH+6V114kTcDjeBVtLAtPwys5ILPNtdwY xLLcx7q5orLlCOyMOOvmqf0SNYl+RD0= To: Pip Cet Subject: Re: bug#75710: 31.0.50; feature/igc: crash report on Arch Linux, 2025-01-20 In-Reply-To: <87v7u67dyb.fsf@protonmail.com> (Pip Cet's message of "Wed, 22 Jan 2025 21:09:58 +0000") References: <874j1t5f75.fsf@wiiw.ac.at> <87o6zzc8i1.fsf@protonmail.com> <87ikq7q9gd.fsf@snapdragon.cc> <87v7u67dyb.fsf@protonmail.com> Date: Wed, 22 Jan 2025 22:32:52 +0100 Message-ID: <87cygezg8r.fsf@snapdragon.cc> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 75710 Cc: 75710@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --=-=-= Content-Type: text/plain Content-Disposition: inline Pip Cet writes: > "Oliver Reiter" writes: > >> Pip Cet writes: >> >>> While unsatisfying, my very preliminary conclusion is that there is a >>> significant chance that this is bug#75754. My plan is to fix this bug >>> unconditionally (without #ifdef HAVE_MPS) on feature/igc because I >>> believe the bug is present, albeit much less likely, on master, and the >>> ultimate fix for bug#75754 is likely to be both very different and take >>> some time. >>> >>> Objections to this? >> >> If you are asking me: no objections. > > A preliminary workaround for bug#75754 has been installed on > feature/igc, erring on the side of protecting too many objects rather > than too few of them. > > I would ask you to please try the current branch, and to report any > further crashes you may see as a new bug; I may be wrong about all your > crashes being due to this bug, but maybe I'm right about one of them :-) > > Thanks for the reports, again! > > If you don't see a crash, can you let us know (without a new bug, > ideally) in a few days, and then we can mark these as probably closed? > > Thanks! Will do, and thank you! >>>> In GNU Emacs 31.0.50 (build 4, x86_64-pc-linux-gnu, GTK+ Version >>>> 3.24.43, cairo version 1.18.2) of 2025-01-20 built on wilap >>>> Repository revision: 35437854166f8d0c1deceb7aba50f27cc838b490 >>>> Repository branch: feature/igc >>>> System Description: Arch Linux >>>> >>>> Configured using: >>>> 'configure 'CFLAGS=-g3 -ggdb -Og -fno-omit-frame-pointer' >>> ^^^ >>> >>> I confess I rarely build with -Og: I'm in the -O0 team, or -Os just to >>> see some different compiler warnings once in a while. Thanks for >>> testing with this flag; it might mean you see bugs others don't. >>> >>> In particular, stack marking with -O0 behaves in a more obvious fashion >>> than in optimized builds; while the intention of -Og is to keep >>> variables in the right location for debugging, I don't know how good GCC >>> is at doing that in practice. >> >> Thanks for the insight, I'll build with -O0 next time. > > I wasn't trying to get you to do that. Not going to stop you either, of > course. All options need to be tested; we just need to find the right > balance between expanding our tests to find all possible crashes and > gathering data on the stability and usability of IGC by running a few > common builds and hoping they don't crash all the time. > > Pip --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Sat Feb 01 18:25:13 2025 Received: (at 75710-done) by debbugs.gnu.org; 1 Feb 2025 23:25:13 +0000 Received: from localhost ([127.0.0.1]:60409 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1teMrR-0008BX-2Z for submit@debbugs.gnu.org; Sat, 01 Feb 2025 18:25:13 -0500 Received: from mail-40131.protonmail.ch ([185.70.40.131]:24107) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1teMrO-00085i-L0 for 75710-done@debbugs.gnu.org; Sat, 01 Feb 2025 18:25:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1738452302; x=1738711502; bh=d7RbEt+JCZI1fDsgu8mgFKiS7PLKja8qy6FKDOa90zE=; 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=jbH6E0eY13VMCiUCv6DY+Ju1PzQ8lmVBfY1/CtO0iAyFykL5IjKeR+CSrOCmQLf9P R6ALNNhSPJ3nYfIu0kgJwBsQtWmafl/+WLwsUvZFRK10oVuWPKcGSmVSPyCAm+bS1r CFy2d8ryn2iUOplAwBnyhI5jZk6ZCbIFN8X2uDmeBGhTHIR5bbaS3MwZ9Fx3OrbKSR 8p7nICql80bLBkdf+ZfdVOmNYm1thwwWttUs0U57UP6dxHSnkpuHGea79gh7WDzwd5 ue9xwGKsqCDjfEp/wH5EkO9ltfTklts+9vY/ToNg30qwnIWVrxrOMSHlq1Pa6Tz5y3 QaG8TkaVZFdPQ== Date: Sat, 01 Feb 2025 23:24:58 +0000 To: Oliver Reiter From: Pip Cet Subject: Re: bug#75710: 31.0.50; feature/igc: crash report on Arch Linux, 2025-01-20 Message-ID: <87wme99rkg.fsf@protonmail.com> In-Reply-To: <87cygezg8r.fsf@snapdragon.cc> References: <874j1t5f75.fsf@wiiw.ac.at> <87o6zzc8i1.fsf@protonmail.com> <87ikq7q9gd.fsf@snapdragon.cc> <87v7u67dyb.fsf@protonmail.com> <87cygezg8r.fsf@snapdragon.cc> Feedback-ID: 112775352:user:proton X-Pm-Message-ID: d623ef4077ea478bc492546e3884f3982918ea6d MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 75710-done Cc: 75710-done@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) "Oliver Reiter" writes: > Pip Cet writes: > >> "Oliver Reiter" writes: >> If you don't see a crash, can you let us know (without a new bug, >> ideally) in a few days, and then we can mark these as probably closed? >> >> Thanks! > > Will do, and thank you! I'm closing this bug as likely caused by the styled_format thing which has been fixed on feature/igc (but, I note, not yet on master), and thus fixed. If it reappears or needs to be reopened, please do so. Thanks for the report and the testing! Pip From unknown Tue Jun 17 20:40:11 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Sun, 02 Mar 2025 12:24:11 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator