GNU bug report logs - #53227
master: Wrong error message with M-: (funcall).

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#53227: closed (master: Wrong error message with M-: (funcall).)
Date: Fri, 14 Jan 2022 17:28:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 14 Jan 2022 12:26:58 -0500
with message-id <jwvwnj2p6sw.fsf-monnier+emacs <at> gnu.org>
and subject line Re: bug#53227: master: Wrong error message with M-: (funcall).
has caused the debbugs.gnu.org bug report #53227,
regarding master: Wrong error message with M-: (funcall).
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
53227: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53227
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Alan Mackenzie <acm <at> muc.de>
To: bug-gnu-emacs <at> gnu.org
Subject: master: Wrong error message with M-: (funcall).
Date: Thu, 13 Jan 2022 07:39:05 +0000

Hello, Emacs.

In the master branch, with emacs -Q, do

    M-: (funcall) RET

..  The error message one sees is

    (void-function nil)

..  This is wrong.  There is no function, nil or otherwise, supplied to
funcall.  The error message ought to be "Too few arguments", or
something like that.

The cause of the bug lies in Ffuncall in .../src/eval.c.  There, the
code uses args[0] without first checking that nargs > 0.

-- 
Alan Mackenzie (Nuremberg, Germany).

[Message part 3 (message/rfc822, inline)]

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 53227-done <at> debbugs.gnu.org, acm <at> muc.de, rpluim <at> gmail.com,
 Andreas Schwab <schwab <at> linux-m68k.org>
Subject: Re: bug#53227: master: Wrong error message with M-: (funcall).
Date: Fri, 14 Jan 2022 12:26:58 -0500

>> The patch should hopefully fix both cases, tho as you can see the two
>> cases are fixed separately (which is what I mean by them being two
>> different bugs).
> I can confirm that this fixes the reported problem (and it doesn't lead
> to any test suite regressions), so please do go ahead and push it.

Done, thanks,


        Stefan

Previous Next

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