From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 10232@debbugs.gnu.org
Subject: bug#10232: 24.0.92; gnus-summary-scroll-up error
Date: Tue, 06 Dec 2011 15:36:59 +0100 [thread overview]
Message-ID: <877h296a2c.fsf@gmail.com> (raw)
In-Reply-To: <jwvhb1dzt4f.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 06 Dec 2011 09:20:22 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> Debugger entered--Lisp error: (error "Invalid byte code in /usr/local/share/emacs/24.0.92/lisp/wid-edit.elc")
>
> You've rebuilt wid-edit.elc after the current process had already
> loaded it. Either restart your Emacs, or just do
> M-x load-library RET wid-edit RET
Ok after restarting emacs, it works again.
> The wid-edit.el file uses `byte-compile-dynamic' which means that when
> you read wid-edit.elc some parts are skipped and replaced by references
> to the corresponding chunk in the file. Those chunks are later fetched
> on demand, but of course, if the file gets modified in the mean time you
> can get into trouble.
> The same trick is used to autoload docstrings, but luckily in the case
> of docstrings the code happens to detect the problem at a stage early
> enough that we can usually fix it (update the references and try again)
> without user intervention.
> For the bytecode refs used with `byte-compile-dynamic' by the time we
> discover the problem, we just have the file name (shown in the error
> message) but not the object that refers to it, so we can't do the fix
> up :-(
Thanks for explanation.
--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
prev parent reply other threads:[~2011-12-06 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 13:35 bug#10232: 24.0.92; gnus-summary-scroll-up error Thierry Volpiatto
2011-12-06 13:57 ` Andreas Schwab
2011-12-06 14:21 ` Thierry Volpiatto
2011-12-06 14:20 ` Stefan Monnier
2011-12-06 14:36 ` Thierry Volpiatto [this message]
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=877h296a2c.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=10232@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).