From: Eli Zaretskii <eliz@gnu.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: gerd.moellmann@gmail.com, 57789@debbugs.gnu.org
Subject: bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x
Date: Sun, 18 Sep 2022 08:33:08 +0300 [thread overview]
Message-ID: <83pmftz1pn.fsf@gnu.org> (raw)
In-Reply-To: <87tu55k90g.fsf@trouble.defaultvalue.org> (message from Rob Browning on Sat, 17 Sep 2022 16:04:31 -0500)
> From: Rob Browning <rlb@defaultvalue.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, 57789@debbugs.gnu.org
> Date: Sat, 17 Sep 2022 16:04:31 -0500
>
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
> > Looking at Rob's backtrace,
> >
> > #0 mark_object (arg=<optimized out>) at alloc.c:6809
> > #1 0x000002aa001a8ee6 in mark_objects (n=<optimized out>, obj=0x2aa00ac54a8) at alloc.c:6607
> > #2 mark_vectorlike (header=0x2aa00ac54a0) at alloc.c:6382
> > #3 0x000002aa001a8ee6 in mark_objects (n=<optimized out>, obj=0x2aa007f4ca8) at alloc.c:6607
> > #4 mark_vectorlike (header=0x2aa007f4ca0) at alloc.c:6382
> > #5 0x000002aa001a8ee6 in mark_objects (n=<optimized out>, obj=0x2aa007c3b10) at alloc.c:6607
> > #6 mark_vectorlike (header=0x2aa007c3b08) at alloc.c:6382
> > #7 0x000002aa001a7c3e in visit_static_gc_roots (visitor=...) at alloc.c:5926
> >
> > and seeing frame#7, would it be a way forward to determine which
> > staticpro (I assume it is a staticpro) that is? Maybe that can give a
> > clue which one can then use together with a bisect, perhaps?
>
> Not completely sure I followed, but moving up to that frame and printing
> visitor didn't work: "optimized out".
The code where this happens is this:
for (int i = 0; i < staticidx; i++)
visitor.visit (staticvec[i], GC_ROOT_STATICPRO, visitor.data);
So one way of knowing which staticpro is being handled here is to see
what is the value of 'i' and look at staticvec[i]. I'm guessing that
'i' is also "optimized out", though, so 2 possible ways forward:
. disassemble visit_static_gc_roots, find in which register or where
on the stack or in memory is 'i; or staticvec[i] stored, and go
from there; or
. add a printf to the above loop to show the value of 'i', and
re-run the build, fingers crossed, hoping that the additional
printf won't make the crash go away.
Once you know which staticpro is being processed here, we'd need to
examine its contents and try to figure out which parts cause the crash
in GC.
Thanks.
next prev parent reply other threads:[~2022-09-18 5:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 1:04 bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x Rob Browning
2022-09-14 2:42 ` Eli Zaretskii
2022-09-14 3:06 ` Rob Browning
2022-09-14 3:20 ` Rob Browning
2022-09-14 20:19 ` Rob Browning
2022-09-14 20:21 ` Rob Browning
2022-09-16 6:04 ` Gerd Möllmann
2022-09-17 21:04 ` Rob Browning
2022-09-18 5:22 ` Gerd Möllmann
2022-09-18 5:49 ` Eli Zaretskii
2022-09-18 5:55 ` Gerd Möllmann
2022-09-18 5:33 ` Eli Zaretskii [this message]
2022-09-24 21:06 ` Rob Browning
2023-06-07 21:15 ` Andrea Corallo
2023-09-11 18:08 ` Stefan Kangas
2022-09-15 7:10 ` Eli Zaretskii
2022-09-15 14:51 ` Paul Eggert via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-15 16:26 ` Rob Browning
2022-09-16 8:43 ` Andrea Corallo
2022-09-16 8:39 ` Andrea Corallo
2022-09-17 21:00 ` Rob Browning
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=83pmftz1pn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57789@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=rlb@defaultvalue.org \
/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).