From: Vibhav Pant <vibhavp@gmail.com>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Mark Oteiza <mvoteiza@udel.edu>, 25716@debbugs.gnu.org
Subject: bug#25716: 26.0.50; Invalid byte opcode: op=0, ptr=30
Date: Tue, 14 Feb 2017 18:31:39 +0530 [thread overview]
Message-ID: <CA+T2Sh3SmeV=QwxWA_=poU2JkFVO8Ngh7unM6s5ujSV6M-O1BQ@mail.gmail.com> (raw)
In-Reply-To: <87zihps1ur.fsf@calancha-pc>
Sorry about that, this seems to be caused by bytecomp.el not
generating correct jump addresses for some tags in the jump table.
I'll try pushing a fix ASAP.
On Tue, Feb 14, 2017 at 12:20 PM, Tino Calancha <tino.calancha@gmail.com> wrote:
> Mark Oteiza <mvoteiza@udel.edu> writes:
>
>>>From -Q:
>>
>> 1. C-x C-f some/patch.diff RET
>> 2. M-n
>>
>> Error running timer: (error "Invalid byte opcode: op=0, ptr=30")
>>
>> In GNU Emacs 26.0.50.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw scroll bars)
>> of 2017-02-13 built on logos
>> Repository revision: fffd4ffd747fe46bb7849a874e4ae265b6eda54e
> it might be cause by the new switch byte-code
> (commit 88549ec38e9bb30e338a9985d0de4e6263b40fb7)
>
> Save the definition of `diff-refine-hunk'
> in a file:
> /tmp/diff-refine-hunk.el
>
> I)
> M-: (load "/tmp/diff-refine-hunk.el") RET
> ;; `diff-hunk-next' works as expected, i.e. with auto refinement.
> II)
> M-: (byte-compile-file "/tmp/diff-refine-hunk.el") RET
> M-: (load "/tmp/diff-refine-hunk.elc") RET
> ;; `diff-hunk-next' doesn't auto refine and it shows
> ;; error "Variable binding depth exceeds max-specpdl-size".
>
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> In GNU Emacs 26.0.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.7)
> of 2017-02-14 built on calancha-pc
> Repository revision: 31b4d9a13741caae2422636d4944212e702b19c3
--
Vibhav Pant
vibhavp@gmail.com
next prev parent reply other threads:[~2017-02-14 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 4:28 bug#25716: 26.0.50; Invalid byte opcode: op=0, ptr=30 Mark Oteiza
2017-02-14 6:50 ` Tino Calancha
2017-02-14 13:01 ` Vibhav Pant [this message]
2017-02-14 15:18 ` Vibhav Pant
2017-02-14 15:47 ` Tino Calancha
2017-02-14 17:40 ` Vibhav Pant
2017-02-14 17:45 ` Mark Oteiza
2017-02-14 20:16 ` Eli Zaretskii
2017-02-15 15:45 ` Vibhav Pant
2017-02-15 16:52 ` 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='CA+T2Sh3SmeV=QwxWA_=poU2JkFVO8Ngh7unM6s5ujSV6M-O1BQ@mail.gmail.com' \
--to=vibhavp@gmail.com \
--cc=25716@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
--cc=tino.calancha@gmail.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).