From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 59213@debbugs.gnu.org
Subject: bug#59213: Emacs 29: Edebug fails to instrument a parameter whose name begins with _
Date: Mon, 14 Nov 2022 07:56:34 -0500 [thread overview]
Message-ID: <jwvsfilhf53.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <Y3IYTSTtOBZSRZ3z@ACM> (Alan Mackenzie's message of "Mon, 14 Nov 2022 10:28:29 +0000")
> More precisely, with this defun:
>
> (defun add (a b c)
> (+ a b))
>
> , instrument it for edebug. Call M-: (add 1 2 6).
>
> The source code with active edebug now looks like:
>
> (defun add (a b c)
> =>(+ a b))
>
> .. `e a` now returns 1. `e b` returns 2. `e c` gives the error message:
>
> Error: Symbol's value as variable is void: c
>
> .. I repeat, this is a bug. It should have returned 6.
[ Well, GDB does the same and claims it's not a bug, instead it says the
variable has been optimized away or something to that effect. ]
Agreed. Edebug should be careful to prevent unused vars from being
optimized away. I'll try and come up with a good patch for that,
Stefan
next prev parent reply other threads:[~2022-11-14 12:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 9:35 bug#59213: Emacs 29: Edebug fails to instrument a parameter whose name begins with _ Alan Mackenzie
2022-11-14 2:48 ` Michael Heerdegen
2022-11-14 3:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-14 10:28 ` Alan Mackenzie
2022-11-14 12:50 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-14 12:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-10 18:51 ` Alan Mackenzie
2023-02-10 22:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-11 7:26 ` Eli Zaretskii
2023-02-13 3:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-13 12:54 ` Eli Zaretskii
2023-02-11 11:17 ` Alan Mackenzie
2023-02-14 21:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-14 22:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-18 18:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-18 18:46 ` Alan Mackenzie
2023-02-20 22:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-15 13:08 ` 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=jwvsfilhf53.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=59213@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=monnier@iro.umontreal.ca \
/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).