unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	54079@debbugs.gnu.org
Subject: bug#54079: 29.0.50; Method dispatching eratically fails
Date: Sat, 5 Mar 2022 19:00:49 +0000	[thread overview]
Message-ID: <YiOzYU+j/f9wFJFP@ACM> (raw)
In-Reply-To: <jwv5yosmgkh.fsf-monnier+emacs@gnu.org>

Hello, Stefan.

On Sat, Mar 05, 2022 at 12:57:09 -0500, Stefan Monnier wrote:
> > I think this problem can only happen for defuns/defvars/defconts inside
> > eval-when-compile or eval-and-compile.
> > Would you try out the following patch, please, which I believe fixes the
> > bug.

> Any chance we could fix it in `bytecomp.el` by calling
> `byte_run_strip_symbol_positions` before evaluating the contents of
> those forms?

I've spent quite a large part of the day trying to get that to work,
without success.  The point is, we want to strip the positions here only
when we're writing the value to a defun/defvar/defconst.
eval-when/and-compile doesn't know what its forms will be doing, and
there's no easy way to find out - for example, there might be a defun in
a nested eval-when/and-compile.  Checking in the defun/defvar/defconst
special forms is direct and economical.

> Maybe we should have a function to check for the absence of
> sympos which we could call (when in debugging mode only) from
> defvar/defalias and friends, which could give us useful backtraces
> showing where/when the sympos "leak"?

That's an interesting idea.  Such a function would differ from
byte-run-strip-symbol-positions only a little bit.

>         Stefan

[ .... ]

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2022-03-05 19:00 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21  0:12 bug#54079: 29.0.50; Method dispatching eratically fails Michael Heerdegen
2022-02-21  1:14 ` Michael Heerdegen
2022-03-04 16:12   ` Lars Ingebrigtsen
2022-02-21  3:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21  4:21   ` Michael Heerdegen
2022-02-22 23:55     ` Michael Heerdegen
2022-02-23  0:27       ` Michael Heerdegen
2022-02-23  0:47         ` Michael Heerdegen
2022-03-04  2:08           ` Michael Heerdegen
2022-03-04 19:11             ` Alan Mackenzie
2022-03-05 16:37             ` Alan Mackenzie
2022-03-05 17:57               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-05 19:00                 ` Alan Mackenzie [this message]
2022-03-05 23:01                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-05 18:19               ` Eli Zaretskii
2022-03-05 19:07                 ` Alan Mackenzie
2022-03-06  2:19               ` Michael Heerdegen
2022-03-08 19:28                 ` Alan Mackenzie
2022-03-08 19:53                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 20:48                     ` Alan Mackenzie
2022-03-08 21:03                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-09 17:42                         ` Alan Mackenzie
2022-03-09 18:06                           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-09 20:32                             ` Alan Mackenzie
2022-03-09 22:04                               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-11 22:01                                 ` Alan Mackenzie
2022-03-12  4:23                                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-13 16:49                                     ` Alan Mackenzie
2022-03-14 12:10                                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-09  4:10                   ` Michael Heerdegen
2022-03-09 17:29                     ` Alan Mackenzie
2022-03-16  1:44                       ` Michael Heerdegen
2022-03-16 11:52                         ` Alan Mackenzie
2022-03-16 19:22                           ` Michael Heerdegen
2022-03-17  2:58                           ` Michael Heerdegen
2022-03-16 19:29                         ` Alan Mackenzie

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=YiOzYU+j/f9wFJFP@ACM \
    --to=acm@muc.de \
    --cc=54079@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael_heerdegen@web.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).