GNU bug report logs - #21821
25.0.50; invalid byte code in dired-x.elc

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21821 in the body.
You can then email your comments to 21821 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Daniel McClanahan <danieldmcclanahan <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.0.50; invalid byte code in dired-x.elc
Date: Tue, 3 Nov 2015 11:53:20 -0600

Byte-compiling lisp/dired-x.el generates invalid byte code in
dired-x.elc, which manifests when attempting to use dired-x functions.
Typically I resolve this by opening and manually evaluating
dired-x.el.

To reproduce on emacs -Q built from master:
1. Byte-recompile dired-x.el
2. Open dired-x.elc.
3. Attempt to evaluate the buffer. It should fail at the attempted
evaluation of `dired-x-bind-find-file' with an "invalid byte code"
error.

Message #8 received at 21821 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: Daniel McClanahan <danieldmcclanahan <at> gmail.com>
Cc: 21821 <at> debbugs.gnu.org
Subject: Re: bug#21821: 25.0.50; invalid byte code in dired-x.elc
Date: Tue, 03 Nov 2015 19:09:24 -0500

Daniel McClanahan wrote:

> Byte-compiling lisp/dired-x.el generates invalid byte code in
> dired-x.elc, which manifests when attempting to use dired-x functions.

I can't reproduce this. You gave no details of platform or anything;
perhaps you need to bootstrap.

> To reproduce on emacs -Q built from master:
> 1. Byte-recompile dired-x.el
> 2. Open dired-x.elc.
> 3. Attempt to evaluate the buffer. It should fail at the attempted
> evaluation of `dired-x-bind-find-file' with an "invalid byte code"
> error.

Did you literally mean what you say, ie visit the .elc file than
evaluate the buffer? I have never thought of doing that with an elc
file, rather than use M-x load-file.

Message #11 received at 21821 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Schwab <schwab <at> suse.de>
To: Daniel McClanahan <danieldmcclanahan <at> gmail.com>
Cc: 21821 <at> debbugs.gnu.org
Subject: Re: bug#21821: 25.0.50; invalid byte code in dired-x.elc
Date: Wed, 04 Nov 2015 09:15:02 +0100

Daniel McClanahan <danieldmcclanahan <at> gmail.com> writes:

> To reproduce on emacs -Q built from master:
> 1. Byte-recompile dired-x.el
> 2. Open dired-x.elc.
> 3. Attempt to evaluate the buffer.

elc files contain special markers that can only be interpreted correctly
by load.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab <at> suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

Message #14 received at 21821 <at> debbugs.gnu.org (full text, mbox):

From: Daniel McClanahan <danieldmcclanahan <at> gmail.com>
To: Andreas Schwab <schwab <at> suse.de>
Cc: 21821 <at> debbugs.gnu.org
Subject: Re: bug#21821: 25.0.50; invalid byte code in dired-x.elc
Date: Wed, 4 Nov 2015 03:39:33 -0600

> elc files contain special markers that can only be interpreted correctly by
> load.

Ok, I wasn't aware of that. I attempted that in the first place because I hit
the same "invalid byte code" error when attempting to use functions defined in
dired-x as they were intended to be used; without evaluating the elc file
manually, within dired, interactively. However, I cannot reproduce those now. I
will update this if I am able to reproduce such an error.

On Wed, Nov 4, 2015 at 2:15 AM, Andreas Schwab <schwab <at> suse.de> wrote:
> Daniel McClanahan <danieldmcclanahan <at> gmail.com> writes:
>
>> To reproduce on emacs -Q built from master:
>> 1. Byte-recompile dired-x.el
>> 2. Open dired-x.elc.
>> 3. Attempt to evaluate the buffer.
>
> elc files contain special markers that can only be interpreted correctly
> by load.
>
> Andreas.
>
> --
> Andreas Schwab, SUSE Labs, schwab <at> suse.de
> GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
> "And now for something completely different."

Message #17 received at 21821 <at> debbugs.gnu.org (full text, mbox):

From: "John Wiegley" <jwiegley <at> gmail.com>
To: Daniel McClanahan <danieldmcclanahan <at> gmail.com>
Cc: Andreas Schwab <schwab <at> suse.de>, 21821 <at> debbugs.gnu.org
Subject: Re: bug#21821: 25.0.50; invalid byte code in dired-x.elc
Date: Wed, 04 Nov 2015 11:16:48 -0500

>>>>> Daniel McClanahan <danieldmcclanahan <at> gmail.com> writes:

> Ok, I wasn't aware of that. I attempted that in the first place because I
> hit the same "invalid byte code" error when attempting to use functions
> defined in dired-x as they were intended to be used; without evaluating the
> elc file manually, within dired, interactively. However, I cannot reproduce
> those now. I will update this if I am able to reproduce such an error.

Can we close the bug now, and reopen if you find a reproduction?

John

Message #20 received at 21821 <at> debbugs.gnu.org (full text, mbox):

From: Daniel McClanahan <danieldmcclanahan <at> gmail.com>
To: John Wiegley <jwiegley <at> gmail.com>
Cc: Andreas Schwab <schwab <at> suse.de>, 21821 <at> debbugs.gnu.org
Subject: Re: bug#21821: 25.0.50; invalid byte code in dired-x.elc
Date: Wed, 4 Nov 2015 11:10:23 -0600

> Can we close the bug now, and reopen if you find a reproduction?

Yes.

On Wed, Nov 4, 2015 at 10:16 AM, John Wiegley <jwiegley <at> gmail.com> wrote:
>>>>>> Daniel McClanahan <danieldmcclanahan <at> gmail.com> writes:
>
>> Ok, I wasn't aware of that. I attempted that in the first place because I
>> hit the same "invalid byte code" error when attempting to use functions
>> defined in dired-x as they were intended to be used; without evaluating the
>> elc file manually, within dired, interactively. However, I cannot reproduce
>> those now. I will update this if I am able to reproduce such an error.
>
> Can we close the bug now, and reopen if you find a reproduction?
>
> John

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.