Subject: Re: bug#57309: 29.0.50; Build error "trying to dump non fixed-up eln file"

From: Gerd Möllmann <[email-masked]>
Date: Sun, 21 Aug 2022 14:28:58 +0200

Lars Ingebrigtsen <[email-masked]> writes:

> Perhaps just "cp -a" the entire build tree over somewhere else, and then
> say "make" there in the copy and see what happens?

Thanks, good idea, and it worked!

In the new lldb session I see that the very first time
dump_native_comp_unit is called, it's aöready failing:

* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
    frame #0: 0x00000001001526cc temacs`dump_native_comp_unit(ctx=0x000000016fdfe300, comp_u=0x0000000107089a68) at pdumper.c:2913:23 [opt]
   2910	dump_native_comp_unit (struct dump_context *ctx,
   2911			       struct Lisp_Native_Comp_Unit *comp_u)
   2912	{
-> 2913	  if (!CONSP (comp_u->file))
   2914	    error ("Trying to dump non fixed-up eln file\n");
   2915	
   2916	  /* Have function documentation always lazy loaded to optimize load-time.  */
Target 0: (temacs) stopped.
(lldb) p comp_u->file
(Lisp_Object) $0 = 0x0000000103911394 (struct Lisp_String *) $2 = 0x0000000103911390
(lldb) p *$2
(struct Lisp_String) $3 = {
  u = {
    s = {
      size = 93
      size_byte = -1
      intervals = NULL
      data = 0x000000011a0158b8 "/Users/gerd/emacs/master2/native-lisp/29_0_50-2dce7c3a/preloaded/window-0d1b8b93-274db3e2.eln"
    }
    next = 0x000000000000005d
    gcaligned = ']'
  }
}

The backtrace is identical to the other debugger session.

Which means that the window.eln cu hasn't been dumped before, which
means what?