From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 13085@debbugs.gnu.org
Subject: bug#13085: 24.3.50; (invalid-function internal--called-interactively-p--get-frame)
Date: Tue, 04 Dec 2012 23:13:51 -0500 [thread overview]
Message-ID: <jwvhao1qgux.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <5BFC29679F4B4C7FBE3B1A3BCA755854@us.oracle.com> (Drew Adams's message of "Tue, 4 Dec 2012 16:44:53 -0800")
> Debugger entered--Lisp error: (invalid-function
> internal--called-interactively-p--get-frame)
> internal--called-interactively-p--get-frame(5)
> #[771 "..." [internal--called-interactively-p--get-frame] 6 "\n\n(fn FRAME1
> FRAME2 I)"](((t apply ad-Advice-narrow-to-region #<subr narrow-to-region> (192
> 262))) ((t apply ad-Advice-narrow-to-region #<subr narrow-to-region> (192 262)))
> (5))
> advice--called-interactively-skip(5 (t ad-Advice-narrow-to-region #<subr narrow-to-region> 192 262) (t apply ad-Advice-narrow-to-region #<subr narrow-to-region> (192 262)))
It looks like your nadvice.el was miscompiled, or compiled with an Emacs
that had an old subr.el (one without the
internal--called-interactively-p--get-frame macro).
My own bootstrapped `emacs' does not suffer from this problem, so I'm
not sure what caused this problem.
Stefan
next prev parent reply other threads:[~2012-12-05 4:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 0:44 bug#13085: 24.3.50; (invalid-function internal--called-interactively-p--get-frame) Drew Adams
2012-12-05 4:13 ` Stefan Monnier [this message]
2012-12-05 4:19 ` Drew Adams
2012-12-05 4:59 ` Stefan Monnier
2012-12-07 17:27 ` Drew Adams
2012-12-07 18:40 ` Dani Moncayo
2012-12-07 18:55 ` Drew Adams
2012-12-07 20:51 ` Drew Adams
2012-12-07 21:36 ` Stefan Monnier
2012-12-07 21:42 ` Eli Zaretskii
2012-12-07 20:31 ` nyc4bos
2012-12-07 21:29 ` Dani Moncayo
2012-12-07 22:19 ` Drew Adams
2012-12-10 22:53 ` nyc4bos
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=jwvhao1qgux.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=13085@debbugs.gnu.org \
--cc=drew.adams@oracle.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).