unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: "make autoloads" signals an error
Date: Wed, 01 Jun 2022 15:44:15 +0300	[thread overview]
Message-ID: <83a6awh7ts.fsf@gnu.org> (raw)
In-Reply-To: <87sfoozi14.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  01 Jun 2022 14:26:31 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 01 Jun 2022 14:26:31 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >   Error: wrong-type-argument (integer-or-marker-p nil)
> >     mapbacktrace(#f(compiled-function (evald func args flags) #<bytecode -0x2d78d25b45e2f81>))
> >     debug-early-backtrace()
> >     debug-early(error (wrong-type-argument integer-or-marker-p nil))
> >     loaddefs-generate(("." "./c
> 
> I'm unable to reproduce this -- "make autoloads" just says
> 
>   GEN      loaddefs.el
>   INFO     Scraping files for loaddefs... 
>   INFO     Scraping files for loaddefs...done

I'm guessing that's because it doesn't regenerate anything.  It fails
for me because it regenerates (a lot of) loaddefs.el, perhaps because
loaddefs-gen.el has changed recent-ish?

> Does "make autoloads-force" also fail for you?

Yes.

> In that case, perhaps there's a bug in the code that's computing the
> updates, and in that case, it depends on which files are newer than
> loaddefs.el.  Hm...
> 
> Could you try removing the "c" from "elc" here:
> 
> $(lisp)/loaddefs.el: gen-lisp $(LOADDEFS)
> 	$(AM_V_GEN)$(emacs) \
>             -l $(lisp)/emacs-lisp/loaddefs-gen.elc \
> 	    -f loaddefs-generate-batch $(lisp)/loaddefs.el ${SUBDIRS_ALMOST}
> 
> That should give us a more detailed backtrace.

Not necessary: I know where it errors out.  It's here:

                  ;; Delete the old version of the section.
                  (delete-region (match-beginning 0)
                                 (and (search-forward "\n\f\n;;;" nil t)
                                      (match-beginning 0)))

And that's because search-forward returns nil:

  Thread 1 hit Breakpoint 2, wrong_type_argument (predicate=XIL(0x8d90), value=XIL(0)) at data.c:142
  142       eassert (!TAGGEDP (value, Lisp_Type_Unused0));
  (gdb) bt
  #0  wrong_type_argument (predicate=XIL(0x8d90), value=XIL(0)) at data.c:142
  #1  0x011acd80 in fix_position (pos=XIL(0)) at buffer.c:143
  #2  0x011b4275 in validate_region (b=0x82f058, e=0x82f050) at buffer.c:2326
  #3  0x0125ba63 in Fdelete_region (start=make_fixnum(23071), end=XIL(0)) <<<<<<
      at editfns.c:2643



  reply	other threads:[~2022-06-01 12:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 12:10 "make autoloads" signals an error Eli Zaretskii
2022-06-01 12:26 ` Lars Ingebrigtsen
2022-06-01 12:44   ` Eli Zaretskii [this message]
2022-06-01 12:46     ` Lars Ingebrigtsen
2022-06-01 12:50       ` Lars Ingebrigtsen
2022-06-01 12:56         ` Lars Ingebrigtsen
2022-06-01 17:51           ` Ergus
2022-06-01 18:21             ` Ergus
2022-06-02  9:16               ` Lars Ingebrigtsen
2022-06-02 10:01                 ` Yuri D'Elia
2022-06-02 10:08                   ` Lars Ingebrigtsen
2022-06-02 10:48                     ` Lars Ingebrigtsen
2022-06-02 10:55                     ` Eli Zaretskii
2022-06-02 11:20                       ` Lars Ingebrigtsen
2022-06-02 11:53                         ` Eli Zaretskii
2022-06-02 11:59                           ` Lars Ingebrigtsen
2022-06-02 12:05                             ` Eli Zaretskii
2022-06-03  3:13                               ` Lars Ingebrigtsen
2022-06-03  5:57                                 ` Eli Zaretskii
2022-06-02 12:54                             ` Andreas Schwab
2022-06-02 11:55               ` Lars Ingebrigtsen
2022-06-01 13:11         ` Eli Zaretskii

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=83a6awh7ts.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).