From: Pieter van Oostrum <pieter-l@vanoostrum.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39962@debbugs.gnu.org, pieter@vanoostrum.org
Subject: bug#39962: 27.0.90; Crash in Emacs 27.0.90
Date: Sat, 07 Mar 2020 20:14:56 +0100 [thread overview]
Message-ID: <lxmu8s7z9r.fsf@cochabamba.vanoostrum.org> (raw)
In-Reply-To: <834kv09h99.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Mar 2020 20:01:06 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>
> Thanks. Since xbacktrace doesn't work in your case for some reason
> (which is troublesome on its own), I will have to ask you to go to
> every frame that calls Ffuncall, and do this:
>
> (gdb) p args[0]
> (gdb) xtype
>
> If "xtype" says it's a symbol, then additionally do this immediately
> after "xtype":
>
> (gdb) xsymbol
>
> This will tell us which Lisp function was called in each such frame: a
> poor man's Lisp backtrace.
>
> Are these problems something you can trigger at will?
Yes. Load a few quite big mailboxes in VM, and do some manipulation on them (like sorting).
Here is the info:
#9 0x0000000100314bfe in Ffuncall (nargs=2, args=0x7ffeefbf6e78)
at eval.c:2796
2796 val = funcall_lambda (fun, numargs, args + 1);
(gdb) p args[0]
$8 = XIL(0xcfeb420)
(gdb) xtype
Lisp_Symbol
(gdb) xsymbol
$9 = (struct Lisp_Symbol *) 0xcfeb5b8
Cannot access memory at address 0xcfeb5c0
(gdb)
#15 0x0000000100314bfe in Ffuncall (nargs=2, args=0x7ffeefbf8e48)
at eval.c:2796
2796 val = funcall_lambda (fun, numargs, args + 1);
(gdb) p args[0]
$10 = XIL(0x105c5b465)
(gdb) xtype
Lisp_Vectorlike
PVEC_COMPILED
(gdb)
#21 0x0000000100314bae in Ffuncall (nargs=3, args=0x7ffeefbf9198)
at eval.c:2794
2794 val = funcall_subr (XSUBR (fun), numargs, args + 1);
(gdb) p args[0]
$11 = XIL(0x5fb6d60)
(gdb) xtype
Lisp_Symbol
(gdb) xsymbol
$12 = (struct Lisp_Symbol *) 0x5fb6ef8
Cannot access memory at address 0x5fb6f00
(gdb)
#24 0x0000000100314bfe in Ffuncall (nargs=1, args=0x7ffeefbfa1b8)
at eval.c:2796
2796 val = funcall_lambda (fun, numargs, args + 1);
(gdb) p args[0]
$13 = XIL(0x3e34910)
(gdb) xtype
Lisp_Symbol
(gdb) xsymbol
$14 = (struct Lisp_Symbol *) 0x3e34aa8
Cannot access memory at address 0x3e34ab0
(gdb)
#27 0x0000000100314bfe in Ffuncall (nargs=10, args=0x7ffeefbfb608)
at eval.c:2796
2796 val = funcall_lambda (fun, numargs, args + 1);
(gdb) p args[0]
$15 = XIL(0x56c6a00)
(gdb) xtype
Lisp_Symbol
(gdb) xsymbol
$16 = (struct Lisp_Symbol *) 0x56c6b98
Cannot access memory at address 0x56c6ba0
(gdb)
#30 0x0000000100314bfe in Ffuncall (nargs=3, args=0x7ffeefbfc958)
at eval.c:2796
2796 val = funcall_lambda (fun, numargs, args + 1);
(gdb) p args[0]
$17 = XIL(0x4a62fc0)
(gdb) xtype
Lisp_Symbol
(gdb) xsymbol
$18 = (struct Lisp_Symbol *) 0x4a63158
Cannot access memory at address 0x4a63160
(gdb)
#31 0x00000001002fd9ca in Ffuncall_interactively (nargs=3, args=0x7ffeefbfc958)
at callint.c:254
254 return unbind_to (speccount, Ffuncall (nargs, args));
(gdb) p args[0]
$19 = XIL(0x4a62fc0)
(gdb) xtype
Lisp_Symbol
(gdb) xsymbol
$20 = (struct Lisp_Symbol *) 0x4a63158
Cannot access memory at address 0x4a63160
(gdb)
#33 0x0000000100314bae in Ffuncall (nargs=4, args=0x7ffeefbfc950)
at eval.c:2794
2794 val = funcall_subr (XSUBR (fun), numargs, args + 1);
(gdb) p args[0]
$21 = XIL(0x62a0)
(gdb) xtype
Lisp_Symbol
(gdb) xsymbol
$22 = (struct Lisp_Symbol *) 0x6438
Cannot access memory at address 0x6440
(gdb)
#37 0x0000000100314bae in Ffuncall (nargs=4, args=0x7ffeefbfd9b8)
at eval.c:2794
2794 val = funcall_subr (XSUBR (fun), numargs, args + 1);
(gdb) p args[0]
$23 = XIL(0x5f592d0)
(gdb) xtype
Lisp_Symbol
(gdb) xsymbol
$24 = (struct Lisp_Symbol *) 0x5f59468
Cannot access memory at address 0x5f59470
(gdb)
#40 0x0000000100314bfe in Ffuncall (nargs=2, args=0x7ffeefbfea18)
at eval.c:2796
2796 val = funcall_lambda (fun, numargs, args + 1);
(gdb) p args[0]
$25 = XIL(0x3960)
(gdb) xtype
Lisp_Symbol
(gdb) xsymbol
$26 = (struct Lisp_Symbol *) 0x3af8
Cannot access memory at address 0x3b00
(gdb)
There seems to be something fishy with the Lisp memory.
--
Pieter van Oostrum
www: http://pieter.vanoostrum.org/
PGP key: [8DAE142BE17999C4]
next prev parent reply other threads:[~2020-03-07 19:14 UTC|newest]
Thread overview: 119+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 23:55 bug#39962: 27.0.90; Crash in Emacs 27.0.90 Pieter van Oostrum
2020-03-07 7:48 ` Eli Zaretskii
2020-03-07 8:40 ` Pieter van Oostrum
2020-03-07 8:41 ` Pieter van Oostrum
2020-03-07 10:51 ` Eli Zaretskii
2020-03-07 11:06 ` Pieter van Oostrum
2020-03-07 13:10 ` Eli Zaretskii
2020-03-07 15:06 ` Pieter van Oostrum
2020-03-07 15:17 ` Eli Zaretskii
2020-03-07 15:49 ` Pieter van Oostrum
2020-03-07 16:07 ` Eli Zaretskii
2020-03-07 17:21 ` Pieter van Oostrum
2020-03-07 18:01 ` Eli Zaretskii
2020-03-07 19:14 ` Pieter van Oostrum [this message]
2020-03-07 19:21 ` Eli Zaretskii
2020-03-07 22:07 ` Pieter van Oostrum
2020-03-09 4:00 ` Pip Cet
2020-03-08 7:42 ` Paul Eggert
2020-03-08 9:34 ` Pieter van Oostrum
2020-03-08 10:05 ` Paul Eggert
2020-03-08 21:37 ` Pieter van Oostrum
2020-03-08 21:58 ` Pieter van Oostrum
2020-03-08 22:34 ` Paul Eggert
2020-03-08 23:58 ` Pieter van Oostrum
2020-03-09 0:01 ` Paul Eggert
2020-03-09 13:26 ` Pieter van Oostrum
2020-03-09 17:10 ` Eli Zaretskii
2020-03-09 19:48 ` Pieter van Oostrum
2020-03-10 13:37 ` Pieter van Oostrum
2020-03-09 19:51 ` Paul Eggert
2020-03-09 21:32 ` Pieter van Oostrum
2020-03-10 10:52 ` Pieter van Oostrum
2020-03-10 14:19 ` Pip Cet
2020-03-10 16:36 ` Pieter van Oostrum
2020-03-11 14:32 ` Pip Cet
2020-03-11 15:16 ` Pieter van Oostrum
2020-03-11 15:43 ` Pip Cet
2020-03-11 15:51 ` Paul Eggert
2020-03-11 16:21 ` Eli Zaretskii
2020-03-11 17:52 ` Eli Zaretskii
2020-03-11 18:53 ` Pip Cet
2020-03-11 19:34 ` Eli Zaretskii
2020-03-12 10:32 ` Pip Cet
2020-03-12 15:23 ` Eli Zaretskii
2020-03-12 20:36 ` Pip Cet
2020-03-13 9:39 ` Eli Zaretskii
2020-03-13 13:56 ` Pip Cet
2020-03-13 16:30 ` Eli Zaretskii
2020-03-14 9:02 ` Pip Cet
2020-03-14 15:39 ` Pip Cet
2020-03-14 16:00 ` Paul Eggert
2020-03-14 16:15 ` Pip Cet
2020-03-14 16:57 ` Eli Zaretskii
2020-03-14 18:34 ` Pip Cet
2020-03-14 19:09 ` Paul Eggert
2020-03-14 20:10 ` Eli Zaretskii
2020-03-15 12:12 ` Pip Cet
2020-03-15 14:53 ` Eli Zaretskii
2020-03-15 12:09 ` Pip Cet
2020-03-15 14:50 ` Eli Zaretskii
2020-03-16 16:31 ` Stefan Monnier
2020-03-11 20:03 ` Pieter van Oostrum
2020-03-12 13:55 ` Pip Cet
2020-03-12 18:13 ` Pieter van Oostrum
2020-03-12 20:00 ` Pip Cet
2020-03-13 8:09 ` Eli Zaretskii
2020-03-13 8:39 ` Pip Cet
2020-03-13 9:19 ` Eli Zaretskii
2020-03-13 17:43 ` Pieter van Oostrum
2020-03-14 3:38 ` Richard Stallman
2020-03-14 8:37 ` Eli Zaretskii
2020-03-14 9:16 ` Pip Cet
2020-03-14 15:34 ` Pip Cet
2020-03-13 17:42 ` Pieter van Oostrum
2020-03-13 19:34 ` Eli Zaretskii
2020-03-13 21:35 ` Pieter van Oostrum
2020-03-14 8:08 ` Eli Zaretskii
2020-03-14 21:32 ` Pieter van Oostrum
2020-03-15 19:49 ` Pieter van Oostrum
2020-03-15 19:57 ` Eli Zaretskii
2020-03-15 23:26 ` Pieter van Oostrum
2020-03-16 10:44 ` Pieter van Oostrum
2020-03-16 15:07 ` Eli Zaretskii
2020-03-16 15:33 ` Pip Cet
2020-03-16 17:19 ` Pip Cet
2020-03-17 3:29 ` Pieter van Oostrum
2020-03-17 4:54 ` Pip Cet
2020-03-17 5:20 ` Pip Cet
2020-03-17 8:45 ` Pieter van Oostrum
2020-03-17 13:54 ` Pip Cet
2020-03-17 15:27 ` Pieter van Oostrum
2020-03-17 20:16 ` Pip Cet
2020-03-17 23:32 ` Pieter van Oostrum
2020-03-18 15:05 ` Eli Zaretskii
2020-03-19 13:23 ` Pieter van Oostrum
2020-03-19 13:57 ` Pip Cet
2020-03-21 21:22 ` Pieter van Oostrum
2020-03-22 14:21 ` Eli Zaretskii
2020-03-22 15:48 ` Pip Cet
2020-03-23 19:34 ` Pip Cet
2020-03-17 8:40 ` Pieter van Oostrum
2020-03-17 15:33 ` Eli Zaretskii
2020-03-17 20:59 ` Paul Eggert
2020-03-18 6:17 ` Pip Cet
2020-03-18 9:22 ` Robert Pluim
2020-03-18 11:38 ` Pieter van Oostrum
2020-03-18 11:57 ` Paul Eggert
2020-03-18 14:08 ` Pip Cet
2020-03-19 19:17 ` Pieter van Oostrum
2020-03-19 19:31 ` Pip Cet
2020-03-19 21:30 ` Pieter van Oostrum
2020-03-18 14:08 ` Eli Zaretskii
2020-03-16 18:36 ` Pieter van Oostrum
2020-03-13 7:58 ` Eli Zaretskii
2020-03-10 15:10 ` Eli Zaretskii
2020-03-10 18:23 ` Pieter van Oostrum
2020-03-11 8:22 ` Paul Eggert
2022-04-30 12:38 ` Lars Ingebrigtsen
2022-05-29 13:19 ` Lars Ingebrigtsen
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=lxmu8s7z9r.fsf@cochabamba.vanoostrum.org \
--to=pieter-l@vanoostrum.org \
--cc=39962@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=pieter@vanoostrum.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 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).