From: Eli Zaretskii <eliz@gnu.org>
To: Vivek Dasmohapatra <vivek@etla.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 17:59:10 +0300 [thread overview]
Message-ID: <837f08xbup.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1706190148280.17706@platypus.pepperfish.net> (message from Vivek Dasmohapatra on Mon, 19 Jun 2017 01:57:54 +0100 (BST))
> Date: Mon, 19 Jun 2017 01:57:54 +0100 (BST)
> From: Vivek Dasmohapatra <vivek@etla.org>
> cc: 26932@debbugs.gnu.org
>
> 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.
I think you should go back along last_marked[] and look for some valid
identifiable object.
> 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.
Indeed. The exact evaluation is not really relevant because the
problem is with an object Emacs is trying to mark, which is most
probably unrelated to what's involved in the :eval form.
next prev parent reply other threads:[~2017-06-19 14:59 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
2017-06-19 14:59 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837f08xbup.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26932@debbugs.gnu.org \
--cc=vivek@etla.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.