Re: Tramp with global-auto-revert-mode.

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sun, 16 May 2004 13:11:03 -0500 (CDT)
> From: Luc Teirlinck <teirllm@dms.auburn.edu>
> 
> I have trouble making sense of the contents of last_marked

You need to look backwards in last_marked starting with
last_marked_index, like you did, but to look at the GC code as you
go.

The part of GC where your session crashed examines live Lisp objects
and marks all of the components of each object (so that the following
sweep step will not garbage-collect what is still in use).  Some Lisp
data structures are marked by looping inside the same invocation of
mark_object; others cause mark_object to be invoked recursively.  By
contrast, the objects in last_marked[] array are recorded
chronologically as they are marked, and the recursive invocations are
not visible there.  So, to find out which Lisp data structure was
being marked, you need to identify what object in last_marked[]
corresponds to each recursive invocation of mark_object that you see
in the backtrace.  That would hopefully give a hint as to where to
look for the villain(s).

Does that help?