From: Alan Mackenzie <acm@muc.de>
To: Andreas Schwab <schwab@suse.de>
Cc: "John Wiegley" <jwiegley@gmail.com>,
20241@debbugs.gnu.org, "Johan Bockgård" <bojohan@gnu.org>,
"Artur Malabarba" <bruce.connor.am@gmail.com>
Subject: bug#20241: 25.0.50; `setq' with only one argument
Date: Thu, 26 Nov 2015 12:06:19 +0000 [thread overview]
Message-ID: <20151126120619.GB1738@acm.fritz.box> (raw)
In-Reply-To: <mvmsi3tkugw.fsf@hawking.suse.de>
Hello, Andreas.
On Thu, Nov 26, 2015 at 09:58:39AM +0100, Andreas Schwab wrote:
> Johan Bockgård <bojohan@gnu.org> writes:
> > (funcall) (print t)
> > Compile. Load .elc =>
> > This consistently gives me one of two results:
> > A segfault, or "Invalid function: 183795961" where the actual
> > number depends on the timestamp of the .elc file.
> That's a bug in the byte compiler, it shouldn't generate call 0 without
> an operand on the stack.
Try the following fix:
diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el
index ffe73de..842e73d 100644
--- a/lisp/emacs-lisp/bytecomp.el
+++ b/lisp/emacs-lisp/bytecomp.el
@@ -4012,8 +4012,12 @@ byte-compile-while
(setq byte-compile--for-effect nil)))
(defun byte-compile-funcall (form)
- (mapc 'byte-compile-form (cdr form))
- (byte-compile-out 'byte-call (length (cdr (cdr form)))))
+ (if (cdr form)
+ (progn
+ (mapc 'byte-compile-form (cdr form))
+ (byte-compile-out 'byte-call (length (cdr (cdr form)))))
+ (byte-compile-log-warning "`funcall' called with no arguments" nil :error)
+ (byte-compile-form '(signal 'wrong-number-of-arguments '(funcall 0)))))
\f
;; let binding
> Andreas.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2015-11-26 12:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 14:53 bug#20241: 25.0.50; `setq' with only one argument Drew Adams
2015-04-01 16:41 ` Stefan Monnier
[not found] ` <mailman.3138.1427900048.31049.bug-gnu-emacs@gnu.org>
2015-11-23 14:31 ` Alan Mackenzie
2015-11-23 18:44 ` Glenn Morris
2015-11-23 18:54 ` Glenn Morris
2015-11-23 22:05 ` John Wiegley
2015-11-23 19:31 ` Alan Mackenzie
2015-11-24 11:32 ` Alan Mackenzie
2015-11-24 17:38 ` Glenn Morris
2015-11-24 18:04 ` Alan Mackenzie
2015-11-24 19:26 ` Artur Malabarba
2015-11-24 21:09 ` Alan Mackenzie
2015-11-25 1:46 ` John Wiegley
2015-11-25 9:41 ` Alan Mackenzie
2015-11-25 10:36 ` Artur Malabarba
2015-11-25 11:07 ` Alan Mackenzie
2015-11-25 11:13 ` Artur Malabarba
2015-11-25 11:28 ` Alan Mackenzie
2015-11-25 15:18 ` Drew Adams
2015-11-25 15:40 ` Alan Mackenzie
2015-11-25 16:27 ` Drew Adams
2015-11-25 17:22 ` Alan Mackenzie
2015-11-25 18:28 ` Drew Adams
2015-11-25 19:06 ` John Wiegley
2015-11-25 19:21 ` John Mastro
2015-11-25 19:22 ` Drew Adams
2015-11-25 19:34 ` Artur Malabarba
2015-11-25 19:40 ` John Wiegley
2015-11-25 20:20 ` Artur Malabarba
2015-11-25 20:37 ` John Wiegley
2015-11-26 11:07 ` Alan Mackenzie
2015-11-25 20:58 ` Alan Mackenzie
2015-11-25 21:19 ` Drew Adams
2015-11-25 21:52 ` John Wiegley
2015-11-26 0:21 ` Johan Bockgård
2015-11-26 8:58 ` Andreas Schwab
2015-11-26 12:06 ` Alan Mackenzie [this message]
2015-11-26 16:38 ` Artur Malabarba
2015-11-26 21:19 ` Alan Mackenzie
2015-11-27 0:07 ` Artur Malabarba
2015-11-25 13:11 ` Nicolas Richard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151126120619.GB1738@acm.fritz.box \
--to=acm@muc.de \
--cc=20241@debbugs.gnu.org \
--cc=bojohan@gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=jwiegley@gmail.com \
--cc=schwab@suse.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.