From: Pip Cet <pipcet@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrea Corallo <akrl@sdf.org>, 47067@debbugs.gnu.org
Subject: bug#47067: 28.0.50; [feature/native-comp] Crash while scrolling through dispnew.c
Date: Sat, 13 Mar 2021 15:45:52 +0000 [thread overview]
Message-ID: <CAOqdjBd2V1C3070pbn1bLGcjSUmWaYz3asZn58H6-fhQOj-AGQ@mail.gmail.com> (raw)
In-Reply-To: <83mtv7hy5c.fsf@gnu.org>
On Sat, Mar 13, 2021 at 3:27 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > > It's nowhere in the C backtrace, only its caller
> >
> > But it was in one of the previous backtraces?
>
> Too many moons ago. The ABI was bumped since then, and so did the
> *.eln files.
The code you pasted matches c-beginning-of-statement-1, and so does
the Lisp backtrace, so I would suggest we go with it...
> > > > Can you disassemble the function around 0x09c32285 (or, in another
> > > > dump, whatever calls Flss), particularly the 256 bytes or so before
> > > > that EIP?
> > >
> > > Below. The updated address for the caller of Flss is 0x09d82285,
> > > which is not in any function whose name is known to GDB.
> >
> > That's normal, assuming you didn't compile with comp-debug > 0.
>
> If that's normal, why did Andrea say that he didn't see such "??" in
> his backtraces? And if that's because Andrea builds with comp-debug
> above the default zero, then I think either the doc string or the set
> of values (or both) need to be updated:
>
> (defcustom comp-debug 0
> "Debug level for native compilation, a number between 0 and 3.
> This is intended for debugging the compiler itself.
> 0 no debugging output.
> This is the recommended value unless you are debugging the compiler itself.
> 1 emit debug symbols and dump pseudo C code.
> 2 dump gcc passes and libgccjit log file.
> 3 dump libgccjit reproducers."
>
> The first line is somewhat deceptive, as it doesn't say portions of
> the backtrace will be anonymous; the backtrace is useful even if not
> "debugging the compiler itself". And the description of level 1 says
> it will also "dump pseudo C code", which I don't think is needed for
> most of the debugging. Maybe we need an intermediate level that just
> leaves the symbols without dumping the pseudo code?
I think that's an excellent idea.
> > > 0x09d82268: mov %edi,0x4(%esp)
> > > 0x09d8226c: mov %eax,-0xe8(%ebp)
> > > 0x09d82272: mov %edx,-0xe4(%ebp)
> > > 0x09d82278: movl $0x2,(%esp)
> > > 0x09d8227f: call *0x1318(%ebx)
> > > 0x09d82285: mov %edx,-0xec(%ebp) <<<<<<<<<<<<<<<<<<<<
> >
> > So EDI is bunk at this point. Can you go back a bit further to where
> > it's initialized?
>
> Sorry, I don't understand: I gave you the disassembly of 512 bytes
> before, isn't that enough to see where EDI is assigned the value? Or
> what do you mean by "go back"?
It's not enough, no. we're looking for an insn of the form mov XXX,
%edi or lea XXX, %edi, or anything like that.
I'm suspicious because EDI is a register variable that is clobbered
somehow right after a setjmp returned. Which setjmp implementation are
you using? Is it possible that you're on Windows, but unlike other
Windows setjmps, it's unsafe to call your setjmp through a function
pointer?
Pip
next prev parent reply other threads:[~2021-03-13 15:45 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
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 [this message]
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=CAOqdjBd2V1C3070pbn1bLGcjSUmWaYz3asZn58H6-fhQOj-AGQ@mail.gmail.com \
--to=pipcet@gmail.com \
--cc=47067@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.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.