From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: pipcet@protonmail.com, eller.helmut@gmail.com, emacs-devel@gnu.org
Subject: Re: MPS: unable to build due to assertion violation in igc_dump_check_object_starts
Date: Tue, 23 Jul 2024 17:26:29 +0300 [thread overview]
Message-ID: <86zfq889re.fsf@gnu.org> (raw)
In-Reply-To: <m2wmlcp5b1.fsf@pro2.fritz.box> (message from Gerd Möllmann on Tue, 23 Jul 2024 16:10:42 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: Pip Cet <pipcet@protonmail.com>, Helmut Eller <eller.helmut@gmail.com>,
> emacs-devel@gnu.org
> Date: Tue, 23 Jul 2024 16:10:42 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So it looks like dflt_skip(0x1b26ac70) yields some bogus value, but I
> > have no idea what it means or where to look to find the reason(s).
>
> This function checks the consistency of the pdump when it is written. It
> should be the case that the two regions of the dump (hot and cold)
> contain igc_headers that correspond to the relocs that the pdump
> contains.
>
> With i == 1 we are currently in the cold region. It should be the case
> that the igc_headers contained in the cold region are traversable in the
> same way as if the objects in the region had been allocated from MPS.
> That is, we start at the start of the regioni with the first objects,
> then dftl_skip from there we reach the second object, dflt_skip from
> there takes us to the third object and so on.
>
> In the failing case, dflt_skip from p does not take us to the next
> object, as far as the relocs say, So either the igc_header at p is
> somehow wrong or the reloc entry from relocs is wrong.
>
> Maybe one can see from the igc_header at p what object type was dumped
> there? There should be some 32-bit dependency somewhwere since I don't
> see that here on 64 bits.
I don't really understand what I'm doing, but does the below help?
Thread 1 hit Breakpoint 1, emacs_abort () at w32fns.c:11335
11335 {
(gdb) up
#1 0x00eb5540 in terminate_due_to_signal (sig=sig@entry=22,
backtrace_limit=backtrace_limit@entry=2147483647) at emacs.c:470
470 emacs_raise (sig);
(gdb)
#2 0x00f2a81a in die (msg=0x14f8051 <i_fwd+4017> "end == p",
file=0x14f79c8 <i_fwd+2344> "igc.c", line=4820) at alloc.c:8400
8400 terminate_due_to_signal (SIGABRT, INT_MAX);
(gdb)
#3 0x00fee189 in igc_dump_check_object_starts (relocs=0x11d32853,
dump_base=0x1aa41020, hot_start=0x1aa41098, hot_end=0x1b055c70,
cold_start=0x1b081020, heap_end=0x1b1f9e98) at igc.c:4820
4820 eassert (end == p);
(gdb) p obj_size(start)
$1 = 801749580
(gdb) p igc_header_nwords(start)
$2 = 200437395
(gdb) p header_tag(start)
$3 = 0
(gdb) p header_nwords(start)
$4 = 200437395
(gdb) p *(struct igc_header *)start
$5 = {v = 1721744118644157000}
(gdb) p/x *(struct igc_header *)start
$6 = {v = 0x17e4dd2759e72a48}
(gdb) p relocs
$7 = (Lisp_Object) 0x11d32853
(gdb) source .gdbinit
SIGINT is used by the debugger.
Are you sure you want to change it? (y or n) [answered Y; input not from terminal]
Environment variable "DISPLAY" not defined.
Environment variable "TERM" not defined.
Breakpoint 2 at 0xeb54e0: file emacs.c, line 432.
(gdb) p relocs
$8 = XIL(0x11d32853)
(gdb) xtype
Lisp_Cons
(gdb) xcar
$9 = 0x11a5eda3
(gdb) xtype
Lisp_Cons
(gdb) xcar
$10 = 0x1b9b062
(gdb) xtype
Lisp_Int0
(gdb) xint
$11 = 7236632
(gdb) p r
$12 = XIL(0x11a5ed33)
(gdb) xtype
Lisp_Cons
(gdb) xcar
$13 = 0x1b9b022
(gdb) xtype
Lisp_Int0
(gdb) xint
$14 = 7236616
(gdb) pp r
(7236616 7236632)
So relocs seem to be pairs of numbers, and 'r', the one that seems to
cause the problem, looks okay to me. But is the igc_header okay?
Let me know if I can collect more data.
next prev parent reply other threads:[~2024-07-23 14:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 12:58 MPS: unable to build due to assertion violation in igc_dump_check_object_starts Eli Zaretskii
2024-07-23 14:10 ` Gerd Möllmann
2024-07-23 14:26 ` Eli Zaretskii [this message]
2024-07-23 14:40 ` Eli Zaretskii
2024-07-23 14:52 ` Gerd Möllmann
2024-07-23 15:43 ` Eli Zaretskii
2024-07-23 16:29 ` Gerd Möllmann
2024-07-23 18:00 ` Eli Zaretskii
2024-07-23 18:37 ` Eli Zaretskii
2024-07-23 18:40 ` Pip Cet
2024-07-23 18:48 ` Gerd Möllmann
2024-07-23 19:12 ` Pip Cet
2024-07-23 19:25 ` Gerd Möllmann
2024-07-23 19:30 ` Gerd Möllmann
2024-07-23 22:47 ` Pip Cet
2024-07-24 3:50 ` Gerd Möllmann
2024-07-24 11:27 ` Eli Zaretskii
2024-07-24 8:01 ` Helmut Eller
2024-07-24 8:21 ` Pip Cet
2024-07-24 8:33 ` Helmut Eller
2024-07-24 9:20 ` Pip Cet
2024-07-24 9:39 ` Helmut Eller
2024-07-24 9:54 ` Pip Cet
2024-07-24 11:40 ` Helmut Eller
2024-07-24 12:25 ` Pip Cet
2024-07-24 11:44 ` Eli Zaretskii
2024-07-23 18:50 ` Gerd Möllmann
2024-07-23 18:42 ` Gerd Möllmann
2024-07-23 18:49 ` Eli Zaretskii
2024-07-23 18:59 ` Gerd Möllmann
2024-07-23 14:42 ` Pip Cet
2024-07-23 16:28 ` Pip Cet
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zfq889re.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.