From: Eval EXEC <execvy@gmail.com>
To: Pip Cet <pipcet@protonmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [scratch/igc] 985247b6bee crash on Linux, KDE, Wayland
Date: Thu, 05 Sep 2024 19:15:10 +0800 [thread overview]
Message-ID: <87bk124aip.fsf@gmail.com> (raw)
In-Reply-To: <87plpis6ff.fsf@protonmail.com> (Pip Cet's message of "Thu, 05 Sep 2024 11:09:49 +0000")
Pip Cet <pipcet@protonmail.com> writes:
> "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'm useing CPU: 13th Gen Intel(R) Core(TM) i9-13900H (20) @ 5.40 GHz
> I'd recommend these CFLAGS:
>
> -g3 -ggdb -fno-omit-frame-pointer
>
> in addition to what you have.
Thank you, now I'm going to compile scratch/igc branch by these CFLAGS.
> Can you disassemble 'copy_font_spec' and 'Flist' by running:
>
> $ gdb /path/to/emacs
> (gdb) disass copy_font_spec
> (gdb) disass Flist
Sorry, I have deleted the core dump file and the emacs binary.
> 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.
Thank you, now I'm going to recompile emacs by:
make extraclean
./autogen.sh \
&& ./configure CFLAGS='-g3 -ggdb -O2 -fno-omit-frame-pointer -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
Do you think it's right?
--
next prev parent reply other threads:[~2024-09-05 11:15 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
2024-09-05 11:15 ` Eval EXEC [this message]
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=87bk124aip.fsf@gmail.com \
--to=execvy@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=pipcet@protonmail.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).