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 21:49:58 +0300 [thread overview]
Message-ID: <86ed7k7xk9.fsf@gnu.org> (raw)
In-Reply-To: <m2jzhcospb.fsf@pro2.fritz.box> (message from Gerd Möllmann on Tue, 23 Jul 2024 20:42:56 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: pipcet@protonmail.com, eller.helmut@gmail.com, emacs-devel@gnu.org
> Date: Tue, 23 Jul 2024 20:42:56 +0200
>
> We are inside of the dump_igc_finish_obj. I see nothing immediately
> suspicious there, hm.
>
> Can you try to look at that header? It is at offset ctx->igc_base_offset
> from ctx->buf. Something like
>
> p header_type ((char *) ctx->buf + ctx->igc_base_offset)
>
> Is it already broken? Depending on where exactly you emacs_abort it
> either should still be zeroed or contain something valid like type
> IGC_OBJ_STRING_DATA.
I added emacs_abort here:
if (ctx->flags.dump_object_contents)
{
char *base = (char *) ctx->buf + ctx->igc_base_offset;
char *end = (char *) ctx->buf + ctx->offset;
if (ctx->igc_base_offset == 0x6e6c08)
emacs_abort (); <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
eassert (end > base);
char *should_end = igc_dump_finish_obj (ctx->igc_obj_dumped, ctx->igc_type, base, end);
eassert (should_end >= end);
dump_write_zero (ctx, should_end - end);
if (ctx->flags.record_object_starts)
dump_push (&ctx->igc_object_starts,
list2 (dump_off_to_lisp (ctx->igc_base_offset),
dump_off_to_lisp (ctx->offset)));
}
And:
(gdb) p header_type ((char *) ctx->buf + ctx->igc_base_offset)
$10 = IGC_OBJ_STRING_DATA
This is _before_ igc_dump_finish_obj was called.
next prev parent reply other threads:[~2024-07-23 18:49 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
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 [this message]
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
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=86ed7k7xk9.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 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).