From: Vivek Dasmohapatra <vivek@etla.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26932@debbugs.gnu.org
Subject: bug#26932: 25.1; Crash triggered a few times a day with network process
Date: Mon, 19 Jun 2017 01:57:54 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.02.1706190148280.17706@platypus.pepperfish.net> (raw)
In-Reply-To: <83d1a52tq6.fsf@gnu.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 3549 bytes --]
> The faulty object would be a very important clue. Once we find that
> out, we should look at how that object is created and modified.
Not sure I'm doing this right, but here's what I have so far:
SEGV @
#0 mark_object; alloc.c:6450
last_mark_index=12, therefore last_mark[11] must be what we are looking at.
(gdb) p XTYPE(last_marked[11])
$41 = Lisp_Symbol
(gdb) p XSYMBOL(last_marked[11])
$44 = (struct Lisp_Symbol *) 0x3c382c0
(gdb) p *XSYMBOL(last_marked[11])
Cannot access memory at address 0x3c382c0
which matches alloc.c:6540 which is inside a `case Lisp_Symbol:' section
line that fails is:
if (ptr->gcmarkbit)
so we have a duff symbol?
============================================================================
#1 mark_object; alloc.c:6543
inside a case Lisp_Cons:
mark_object (ptr->car);
assuming this is the previous marked object:
(gdb) p XTYPE(last_marked[10])
$45 = Lisp_Cons
(gdb) p XCONS(last_marked[10])
$46 = (struct Lisp_Cons *) 0x2eaf810
(gdb) p *XCONS(last_marked[10])
$47 = {car = 50828624, u = {cdr = 48953347, chain = 0x2eaf803}}
(gdb) p XTYPE(50828624)
$49 = Lisp_Symbol
(gdb) p *XSYMBOL(50828624)
Cannot access memory at address 0x3c382c0 // curses, foiled again
============================================================================
#2 mark_maybe_object; alloc.c:4743
Not interesting: checks for alive-ness and calls mark_object
============================================================================
#3 mark_memory (end=0x7fffffffe218, start=<optimized out>); alloc.c:4895
for (pp = start; (void *) pp < end; pp += GC_POINTER_ALIGNMENT)
{
mark_maybe_pointer (*(void **) pp);
mark_maybe_object (*(Lisp_Object *) pp); // ← this is the entry point
}
(gdb) p XTYPE(*(Lisp_Object *)pp)
$63 = Lisp_Cons
(gdb) p *XCONS(*(Lisp_Object *)pp)
$65 = {car = 48892595, u = {cdr = 49727219, chain = 0x2f6c6f3}}
This doesn't seem to match what we encounter two frames down in mark_object:
Maybe I've misinterpreted something? Anyway:
following the earlier call to mark_maybe_pointer:
(gdb) call mem_find(*((void **) pp))
$86 = (struct mem_node *) 0x2cce8a0
(gdb) p *(struct mem_node *) 0x2cce8a0
$87 = {left = 0x2cce8e0, right = 0x2e816e0, parent = 0x2d5cb00,
start = 0x2f6c400, end = 0x2f6c7f0, color = MEM_BLACK, type = MEM_TYPE_CONS}
and later on:
case MEM_TYPE_CONS:
if (live_cons_p (m, p) && !CONS_MARKED_P ((struct Lisp_Cons *) p))
XSETCONS (obj, p);
break;
so we've copied the cons cell into obj (I think).
And then finally:
if (!NILP (obj))
mark_object (obj);
so maybe last_marked[9] is involved?
idx 9 seems to be a list with every car being:
(gdb) p last_marked[9]
$120 = 48953379
(gdb) p XTYPE(last_marked[9])
$121 = Lisp_Cons
(gdb) p *XCONS(last_marked[9])
$122 = {car = 8760836, u = {cdr = 48953363, chain = 0x2eaf813}}
(gdb) p XTYPE(8760836)
$123 = Lisp_String
(gdb) p *XSTRING(8760836)
$124 = {size = 4, size_byte = -1, intervals = 0x0,
data = 0xb374bb <pure+2999995> "DEAD"}
So... a reaped list? Not helpful anyway. Nothing identifiable here.
============================================================================
#4 mark_stack
Nothing of note here
============================================================================
Going up the backtrace all I find is that we're in the modeline display
code and we're _about_ to eval the mode-line-frame-identification
value:
(:eval (mode-line-frame-control))
But GC happens before we actually call it.
Not sure where to go from here: Any advice?
next prev parent reply other threads:[~2017-06-19 0:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 20:54 bug#26932: 25.1; Crash triggered a few times a day with network process Vivek Dasmohapatra
2017-05-15 3:04 ` Eli Zaretskii
2017-05-15 11:18 ` Vivek Dasmohapatra
2017-06-11 21:39 ` Vivek Dasmohapatra
2017-06-12 14:10 ` Eli Zaretskii
2017-06-12 15:21 ` Vivek Dasmohapatra
2017-06-12 15:51 ` Eli Zaretskii
2017-06-12 15:56 ` Vivek Dasmohapatra
2017-06-12 16:30 ` Eli Zaretskii
2017-06-13 15:41 ` Vivek Dasmohapatra
2017-06-13 16:41 ` Eli Zaretskii
2017-06-13 17:04 ` Vivek Dasmohapatra
2017-06-13 19:46 ` Eli Zaretskii
2017-06-13 21:23 ` Vivek Dasmohapatra
2017-06-14 2:32 ` Eli Zaretskii
2017-06-15 13:48 ` Vivek Dasmohapatra
2017-06-15 14:47 ` Eli Zaretskii
2017-06-19 0:57 ` Vivek Dasmohapatra [this message]
2017-06-19 14:59 ` Eli Zaretskii
2017-06-19 18:03 ` Vivek Dasmohapatra
2017-07-10 13:01 ` bug#26932: Subject: Re: bug#26932: 25.1; Vivek Dasmohapatra
2018-01-10 13:58 ` bug#26932: Found the triggering behaviour Vivek Dasmohapatra
2019-10-23 10:02 ` Lars Ingebrigtsen
2020-01-20 15:11 ` Vivek Dasmohapatra
2020-01-22 13:30 ` 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=alpine.DEB.2.02.1706190148280.17706@platypus.pepperfish.net \
--to=vivek@etla.org \
--cc=26932@debbugs.gnu.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 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).