From: Eval EXEC <execvy@gmail.com>
To: Pip Cet <pipcet@protonmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
gerd.moellmann@gmail.com, emacs-devel@gnu.org
Subject: Re: [scratch/igc] 985247b6bee crash on Linux, KDE, Wayland
Date: Fri, 06 Sep 2024 14:39:27 +0800 [thread overview]
Message-ID: <87ed5xxp40.fsf@gmail.com> (raw)
In-Reply-To: <87jzfpfhmf.fsf@protonmail.com> (Pip Cet's message of "Fri, 06 Sep 2024 05:58:34 +0000")
Pip Cet <pipcet@protonmail.com> writes:
> "Eval EXEC" <execvy@gmail.com> writes:
>
>> Eval EXEC <execvy@gmail.com> writes:
>>
>>> I recompiled commit 95a30325a84 (HEAD -> scratch/igc, origin/scratch/igc)
>>> * src/igc.c (fix_frame): Correct the previous change.
>>>
>>> After testing, I believe the issue has been resolved.
>>
>> scratch/igc 95a30325 crash again:
>>
>> I use latest scratch/igc commit: * 95a30325a84 - (HEAD -> scratch/igc, origin/scratch/igc) * src/igc.c (fix_frame): Fix last change. (8 hours ago) <Eli Zaretskii>
>>
>> build it by:
>>
>> #!/usr/bin/env bash
>> set -ex
>>
>> make extraclean
>>
>> BRANCH_NAME=$(git branch --show-current | sed 's/\//_/g')
>> COMMIT_ID=$(git rev-parse --short=8 HEAD)
>> BUILD_DIR=${BRANCH_NAME}-commit-${COMMIT_ID}
>> INSTALL_PREFIX=$(realpath ../emacs-build/${BUILD_DIR})
>>
>> ./autogen.sh
>> ./configure CFLAGS='-g3 -ggdb -O2 -fno-omit-frame-pointer -mtune=native -march=native' \
>> --prefix=${INSTALL_PREFIX} \
>> --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
>>
>> rm ../emacs-build/emacs
>> ln -s ${INSTALL_PREFIX} ../emacs-build/emacs
>
> Thanks, and sorry you're seeing so many crashes. It's stable here, so
> we're going to need your help debugging this :-)
>
> Did you use any special options or patches when building mps (link time
> optimization or -O3, in particular)? Could you please try (but please
> keep the core file and binary for this crash) rebuilding mps with "-g3
> -ggdb -O0" to see whether the problem is, maybe, mps rather than Emacs?
> That should also improve the debugging output, so please provide further
> crashes if they do happen with those options.
>
>> #9 0x0000000000690c05 in fix_lisp_obj (ss=ss@entry=0x7ffc7653e6f8, pobj=pobj@entry=0x7f08addd06b8) at /home/exec/Projects/git.savannah.gnu.org/git/emacs/src/igc.c:975
>
> This is the car of a cons cell, and it looks like it was freed by a
> previous garbage collection so it's no longer valid.
>
>> off = <optimized out>
>> client = <optimized out>
>> base = 0x7f088a262a50
>
> Could you open the coredump again and run
>
> (gdb) x/32gx 0x7f088a262a00
>
> so we can get an idea of what was allocated around that time?
>
>> res = <optimized out>
>> new_off = <optimized out>
>> p = 0x7f08addd06b8
>> word = <optimized out>
>> tag = <optimized out>
>> _ss = 0x7ffc7653e6f8
>> _mps_zs = <optimized out>
>> _mps_ufs = 36029896530599944
>> _mps_wt = <optimized out>
>> _mps_w = <optimized out>
>> #10 0x00000000006919f8 in fix_cons (cons=0x7f08addd06b0, ss=0x7ffc7653e6f8) at /home/exec/Projects/git.savannah.gnu.org/git/emacs/src/igc.c:1751
>
> This is the cons cell itself (the IGC header is what "cons" points to).
>
> Please also run
>
> (gdb) x/64gx 0x7f08addd0600
>
> Thanks!
>
> Pip
Hello Pip, what git commit hash or git tag show I compile from https://github.com/Ravenbrook/mps
Should I compile mps from latest master branch, commit hash:
e2f9497bf3b842fdaa21942da4edd1e6f02b9509 ?
--
next prev parent reply other threads:[~2024-09-06 6:39 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
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 [this message]
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=87ed5xxp40.fsf@gmail.com \
--to=execvy@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--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).