unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pip Cet <pipcet@protonmail.com>
To: Eval EXEC <execvy@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [scratch/igc] 985247b6bee crash on Linux, KDE, Wayland
Date: Thu, 05 Sep 2024 11:09:49 +0000	[thread overview]
Message-ID: <87plpis6ff.fsf@protonmail.com> (raw)
In-Reply-To: <8734mezkgo.fsf@gmail.com>

"Eval EXEC" <execvy@gmail.com> writes:

> Hello,
> I'm helping to test scratch/igc branch, commit: 985247b6bee

Thanks for the reports!

> I build emacs by:
> ```
> make extraclean
> ./autogen.sh \
>   && ./configure CFLAGS='-O3 -mtune=native -march=native' \
>   --prefix=$(realpath ../emacs-build/$(git branch --show-current | sed 's/\//_/g'))\
>   --with-mps=yes \
>   --with-imagemagick  \
>   --with-modules \
>   --without-compress-install \
>   --with-native-compilation  --with-mailutils\
>   --enable-link-time-optimization \
>   --with-tree-sitter --with-xinput2  \
>   --with-dbus  --with-native-compilation=aot \
>   --with-file-notification=inotify\
>   && make -j30 install
> ```

What's your CPU, and which compiler is in use?  "-march=native" means
"optimize for the current CPU", so it's difficult to reproduce crashes
without that knowledge.

I'd recommend these CFLAGS:

-g3 -ggdb -fno-omit-frame-pointer

in addition to what you have.

> #0  0x00007f84a90a2efc in __pthread_kill_implementation () from /nix/store/dbcw19dshdwnxdv5q2g6wldj6syyvq7l-glibc-2.39-52/lib/libc.so.6
> #1  0x00007f84a9052e86 in raise () from /nix/store/dbcw19dshdwnxdv5q2g6wldj6syyvq7l-glibc-2.39-52/lib/libc.so.6
> #2  0x0000000000429886 in terminate_due_to_signal ()
> #3  0x0000000000431d79 in igc_assert_fail.lto_priv[cold] ()
> #4  0x00000000007b0e60 in LockClaim ()
> #5  0x00000000007ddea5 in ArenaEnterLock ()
> #6  0x00000000007e01a1 in mps_ap_fill ()
> #7  0x00000000006e74b6 in alloc_impl.lto_priv ()
> #8  0x000000000060993b in list2 ()
> #9  0x000000000042da87 in xsignal2 ()
> #10 0x000000000042c379 in wrong_type_argument ()
> #11 0x0000000000430730 in get_process.lto_priv[cold] ()
> #12 0x00000000006bd653 in process_send_signal ()
> #13 0x00000000006be017 in kill_buffer_processes ()
> #14 0x000000000058efb5 in shut_down_emacs ()
> #15 0x0000000000429852 in terminate_due_to_signal ()
> #16 0x000000000042a38f in handle_sigsegv.lto_priv[cold] ()
> #17 <signal handler called>
> #18 0x00007f84a905316b in kill () from /nix/store/dbcw19dshdwnxdv5q2g6wldj6syyvq7l-glibc-2.39-52/lib/libc.so.6
> #19 0x00000000007e3919 in sigHandle ()
> #20 <signal handler called>
> #21 0x000000000075d716 in dflt_scan_obj.isra ()
> #22 0x00000000006e288d in dflt_scan ()
> #23 0x00000000007979d6 in amcSegScanNailedRange ()
> #24 0x00000000007b07b2 in amcSegScan ()
> #25 0x00000000007d27fc in traceScanSegRes ()
> #26 0x00000000007d29b9 in traceScanSeg ()
> #27 0x00000000007d31f6 in TraceAdvance ()
> #28 0x00000000007d3771 in TracePoll ()
> #29 0x00000000007d397b in ArenaPoll ()
> #30 0x00000000007e01ef in mps_ap_fill ()
> #31 0x00000000006e74b6 in alloc_impl.lto_priv ()
> #32 0x000000000066f9dc in copy_font_spec ()

Can you disassemble 'copy_font_spec' and 'Flist' by running:

$ gdb /path/to/emacs
(gdb) disass copy_font_spec
(gdb) disass Flist

and post the output?  Also, when you post backtraces, once you've
enabled '-g3 -ggdb', can you try using "bt full" rather than "bt" to get
more useful backtraces?

> What information should I provide to help investigating this?

Ideally, you could run emacs from within gdb and keep the gdb session
open after a crash (but remember to use "handle SIGSEGV nostop pass" if
you don't source .gdbinit which should do that automatically, or it will
stop at the first (harmless) SIGSEGV).  Please let us know if and when
you get a crash that way and we can hopefully debug this further.

Thanks!

Pip




  parent reply	other threads:[~2024-09-05 11:09 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05  6:24 [scratch/igc] 985247b6bee crash on Linux, KDE, Wayland Eval EXEC
2024-09-05  7:14 ` Eval EXEC
2024-09-05  8:17   ` Eval EXEC
2024-09-05  7:21 ` Eval EXEC
2024-09-05  8:08 ` Eli Zaretskii
2024-09-05  8:14   ` Eval EXEC
2024-09-05 11:12   ` Pip Cet
2024-09-05  8:24 ` Helmut Eller
2024-09-05  8:28   ` Eval EXEC
2024-09-05  8:34     ` Helmut Eller
2024-09-05  8:37       ` Eval EXEC
2024-09-05 10:44       ` Eval EXEC
2024-09-05 11:01         ` Eli Zaretskii
2024-09-05 11:04           ` Eval EXEC
2024-09-05 11:09 ` Pip Cet [this message]
2024-09-05 11:15   ` Eval EXEC
2024-09-05 11:19     ` Pip Cet
2024-09-05 11:26       ` Eval EXEC
2024-09-05 16:04         ` Pip Cet
2024-09-05 16:32           ` Eval EXEC
2024-09-05 11:34       ` Eval EXEC
2024-09-05 11:49       ` Eval EXEC
2024-09-05 12:21         ` Eli Zaretskii
2024-09-05 13:20           ` Gerd Möllmann
2024-09-05 13:31             ` Eli Zaretskii
2024-09-05 13:37               ` Gerd Möllmann
2024-09-05 13:52                 ` Eli Zaretskii
2024-09-05 13:57                   ` Gerd Möllmann
2024-09-05 14:33                     ` Eli Zaretskii
2024-09-05 14:44                       ` Eli Zaretskii
2024-09-05 14:58                       ` Gerd Möllmann
2024-09-05 16:19                       ` Pip Cet
2024-09-05 16:40                         ` Eval EXEC
2024-09-05 16:45                         ` Eval EXEC
2024-09-05 16:57                         ` Eval EXEC
2024-09-05 16:59                           ` Eval EXEC
2024-09-05 17:03                           ` Pip Cet
2024-09-05 17:05                             ` Eval EXEC
2024-09-05 17:16                               ` Gerd Möllmann
2024-09-05 18:46                                 ` Eli Zaretskii
2024-09-05 19:24                                   ` Gerd Möllmann
2024-09-05 19:31                                     ` Eli Zaretskii
2024-09-05 18:48                               ` Eli Zaretskii
2024-09-05 18:56                                 ` Eval EXEC
2024-09-05 19:23                                   ` Eli Zaretskii
2024-09-05 19:31                                     ` Eli Zaretskii
2024-09-06  2:15                                     ` Eval EXEC
2024-09-06  3:10                                       ` Eval EXEC
2024-09-06  5:58                                         ` Pip Cet
2024-09-06  6:32                                           ` Eval EXEC
2024-09-06  7:41                                             ` Pip Cet
2024-09-06  8:28                                               ` Eval EXEC
2024-09-06 12:58                                                 ` Pip Cet
2024-09-06 13:14                                                   ` Eval EXEC
2024-09-06 10:57                                               ` Eli Zaretskii
2024-09-06 13:03                                                 ` Eval EXEC
2024-09-06 19:29                                             ` Pip Cet
2024-09-07  5:57                                               ` Eli Zaretskii
2024-09-07  9:05                                                 ` Pip Cet
2024-09-06  6:39                                           ` Eval EXEC
2024-09-06  7:43                                             ` Pip Cet
2024-09-07  7:46                                               ` Eval EXEC
2024-09-07  8:10                                                 ` Pip Cet
2024-09-07 13:20                                                   ` Gerd Möllmann
2024-09-06  6:05                                         ` Eli Zaretskii
2024-09-06  6:30                                           ` Pip Cet
2024-09-06  6:34                                           ` Eval EXEC
2024-09-06 11:49                                             ` Eli Zaretskii
2024-09-06 13:08                                               ` Eval EXEC
2024-09-05 19:01                                 ` Eval EXEC
2024-09-05 17:29                             ` Eval EXEC

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87plpis6ff.fsf@protonmail.com \
    --to=pipcet@protonmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=execvy@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).