From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 47067@debbugs.gnu.org
Subject: bug#47067: 28.0.50; [feature/native-comp] Crash while scrolling through dispnew.c
Date: Sat, 13 Mar 2021 10:34:06 +0200 [thread overview]
Message-ID: <838s6rjvup.fsf@gnu.org> (raw)
In-Reply-To: <xjfzgz816bw.fsf@sdf.org> (message from Andrea Corallo on Fri, 12 Mar 2021 20:10:27 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: 47067@debbugs.gnu.org
> Date: Fri, 12 Mar 2021 20:10:27 +0000
>
> >> > Just evaluating c-beginning-of-statement-1 doesn't help. But if I
> >> > load cc-engine.el, then the crash goes away.
> >>
> >> Okay, then probably is one of the other four c-* functions we see in the
> >> backtrace.
> >
> > Yes, but how to determine which one?
>
> Given they are 4 one could go evaluating these one by one, if they were
> more bisection would have been the best strategy. Yeah that's not the
> most fun...
I was wrong: it _is_ c-beginning-of-statement-1, after all. It's just
that the procedure I followed to evaluate is was wrong. AFAIU now, it
should be: first load-library cc-engine (which loads the .eln file),
then evaluate the function's definition in the .el file.
So now, given that this (humongous) function is the suspect, how do I
proceed with the next steps, which you described as follows:
When the function is identified I typically construct a single function
reproducer, for this I typically need the input parameters and I try to
substitute all other values coming from the environment with something I
can control. This step involves understanding which part of the
environment are captured by the function (say: point, current buffer
content etc etc...).
At that point I reduce the function searching for the minimal piece of
code that behaves differently when native compiled.
At this point will typically start the "smart" part of the
investigation.
> >> To force the .elc to be loaded one has to bind `load-no-native' to
> >> non-nil.
> >
> > I think if load-file is invoked interactively, and the user actually
> > types "foo.elc", we need to bind load-no-native non-nil
> > automatically. Otherwise users would be surprised, as it goes against
> > the logic of what we do when the user types "foo.el".
>
> We certanly can do this if this is what we want. This breaks a little
> the idea to have the system as much transparent as possible, I went this
> way cause this was my understanding of what we wanted but I've no strong
> feeling with that.
I don't think this will break the transparent operation, because
loading a package non-interactively (as in when the corresponding
feature is 'require'd by some code) will still load the .eln file.
Only the following 2 use cases will be affected:
M-x load-file RET /path/to/FOO.elc RET
M-x load-library RET FOO.elc RET
IOW, when the user loads the file/library interactively, and
explicitly uses the .elc extension, we load the file the user
specified, not the corresponding .eln file.
next prev parent reply other threads:[~2021-03-13 8:34 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 11:27 bug#47067: 28.0.50; [feature/native-comp] Crash while scrolling through dispnew.c Eli Zaretskii
2021-03-11 12:19 ` Eli Zaretskii
2021-03-11 14:07 ` Eli Zaretskii
2021-03-12 6:46 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 8:10 ` Eli Zaretskii
2021-03-12 12:04 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 12:51 ` Eli Zaretskii
2021-03-12 15:27 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 15:50 ` Eli Zaretskii
2021-03-12 16:08 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 16:14 ` Eli Zaretskii
2021-03-12 19:30 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 19:48 ` Eli Zaretskii
2021-03-12 20:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 7:11 ` Eli Zaretskii
2021-03-13 19:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 20:07 ` Eli Zaretskii
2021-03-13 20:20 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 7:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 8:02 ` Eli Zaretskii
2021-03-14 8:10 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 19:29 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 19:48 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 16:23 ` Eli Zaretskii
2021-03-12 19:04 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 19:32 ` Eli Zaretskii
2021-03-12 20:10 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 8:34 ` Eli Zaretskii [this message]
2021-03-19 9:42 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-19 12:10 ` Eli Zaretskii
2021-03-19 14:05 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-19 14:09 ` Eli Zaretskii
2021-03-20 9:52 ` Eli Zaretskii
2021-03-21 8:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 9:52 ` Eli Zaretskii
2021-03-21 11:56 ` Eli Zaretskii
2021-03-21 14:37 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 15:34 ` Eli Zaretskii
2021-03-21 15:41 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 15:54 ` Eli Zaretskii
2021-03-21 16:41 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 17:01 ` Eli Zaretskii
2021-03-21 18:36 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-25 16:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-25 17:03 ` Eli Zaretskii
2021-03-25 20:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-25 20:43 ` Eli Zaretskii
2021-04-04 20:52 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-05 15:06 ` Eli Zaretskii
2021-04-05 16:09 ` Eli Zaretskii
2021-04-05 17:58 ` Eli Zaretskii
2021-04-06 13:17 ` Eli Zaretskii
2021-04-06 13:29 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 13:53 ` Eli Zaretskii
2021-04-06 14:01 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-05 18:45 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-05 18:04 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-05 18:19 ` Eli Zaretskii
2021-04-05 18:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-05 19:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 15:49 ` Eli Zaretskii
2021-04-06 16:06 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 16:09 ` Eli Zaretskii
2021-03-21 14:36 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 18:42 ` Pip Cet
2021-03-12 19:50 ` Eli Zaretskii
2021-03-13 8:18 ` Pip Cet
2021-03-13 8:47 ` Eli Zaretskii
2021-03-13 8:53 ` Pip Cet
2021-03-13 11:10 ` Eli Zaretskii
2021-03-13 11:23 ` Eli Zaretskii
2021-03-13 11:24 ` Pip Cet
2021-03-13 15:27 ` Eli Zaretskii
2021-03-13 15:45 ` Pip Cet
2021-03-13 16:21 ` Eli Zaretskii
2021-03-13 16:32 ` Pip Cet
2021-03-13 16:53 ` Eli Zaretskii
2021-03-13 17:10 ` Pip Cet
2021-03-13 17:26 ` Eli Zaretskii
2021-03-13 18:55 ` Pip Cet
2021-03-13 19:43 ` Eli Zaretskii
2021-03-13 20:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 21:00 ` Pip Cet
2021-03-13 21:07 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 21:11 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 6:07 ` Eli Zaretskii
2021-03-14 6:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 7:21 ` Eli Zaretskii
2021-03-14 7:31 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 7:48 ` Eli Zaretskii
2021-03-14 8:02 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 8:06 ` Pip Cet
2021-03-14 11:39 ` Eli Zaretskii
2021-03-14 11:44 ` Pip Cet
2021-03-14 12:08 ` Eli Zaretskii
2021-03-14 12:09 ` Pip Cet
2021-03-14 12:17 ` Pip Cet
2021-03-14 13:31 ` Eli Zaretskii
2021-03-14 14:08 ` Eli Zaretskii
2021-03-14 18:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <83mtv5frr4.fsf@gnu.org>
2021-03-14 20:30 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-15 18:36 ` Eli Zaretskii
2021-03-15 20:17 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 13:25 ` Eli Zaretskii
2021-03-14 8:03 ` Pip Cet
2021-03-14 5:55 ` Eli Zaretskii
2021-03-14 6:57 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 8:20 ` Eli Zaretskii
2021-03-13 17:09 ` Eli Zaretskii
2021-03-14 12:17 ` Eli Zaretskii
2021-03-14 19:00 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 19:48 ` Eli Zaretskii
2021-03-14 20:36 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-15 3:24 ` Eli Zaretskii
2021-03-13 20:03 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=838s6rjvup.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47067@debbugs.gnu.org \
--cc=akrl@sdf.org \
/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.