From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Tramp with global-auto-revert-mode.
Date: 17 May 2004 08:04:06 +0200 [thread overview]
Message-ID: <ud653bne1.fsf@gnu.org> (raw)
In-Reply-To: <200405161811.i4GIB3O03519@raven.dms.auburn.edu> (message from Luc Teirlinck on Sun, 16 May 2004 13:11:03 -0500 (CDT))
> 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?
next prev parent reply other threads:[~2004-05-17 6:04 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 22:54 Tramp with global-auto-revert-mode Luc Teirlinck
2004-05-12 23:26 ` Luc Teirlinck
2004-05-13 23:11 ` Kim F. Storm
2004-05-13 23:24 ` Luc Teirlinck
2004-05-13 23:46 ` Kim F. Storm
2004-05-14 0:08 ` Luc Teirlinck
2004-05-14 1:17 ` Stefan Monnier
2004-05-14 1:32 ` Luc Teirlinck
2004-05-14 2:35 ` Stefan Monnier
2004-05-14 2:53 ` Luc Teirlinck
2004-05-14 3:08 ` Luc Teirlinck
2004-05-14 4:16 ` Stefan Monnier
2004-05-14 4:45 ` Luc Teirlinck
2004-05-14 5:09 ` Stefan Monnier
2004-05-14 19:13 ` Luc Teirlinck
2004-05-14 21:02 ` Richard Stallman
2004-05-14 5:01 ` Luc Teirlinck
2004-05-14 23:00 ` Kim F. Storm
2004-05-15 0:44 ` Luc Teirlinck
2004-05-15 1:39 ` Luc Teirlinck
2004-05-15 18:34 ` Richard Stallman
2004-05-15 20:44 ` Luc Teirlinck
2004-05-15 23:44 ` Luc Teirlinck
2004-05-16 0:41 ` Luc Teirlinck
2004-05-16 13:52 ` Andreas Schwab
2004-05-17 11:04 ` Richard Stallman
2004-05-17 14:20 ` Luc Teirlinck
2004-05-16 5:58 ` Eli Zaretskii
2004-05-16 18:11 ` Luc Teirlinck
2004-05-16 18:32 ` Luc Teirlinck
2004-05-16 20:04 ` Luc Teirlinck
2004-05-16 22:41 ` Kim F. Storm
2004-05-17 5:21 ` Kai Grossjohann
2004-05-17 12:45 ` Kim F. Storm
2004-05-17 15:03 ` Luc Teirlinck
2004-05-17 15:22 ` Kim F. Storm
2004-05-18 16:25 ` Stefan Monnier
2004-05-18 17:10 ` Luc Teirlinck
2004-05-21 23:44 ` Kim F. Storm
2004-05-22 1:08 ` Luc Teirlinck
2004-05-22 11:52 ` Kim F. Storm
2004-05-23 17:21 ` Michael Albinus
2004-05-17 6:04 ` Eli Zaretskii [this message]
2004-05-15 2:50 ` Luc Teirlinck
2004-05-15 13:19 ` Andreas Schwab
2004-05-15 13:34 ` Luc Teirlinck
2004-05-15 16:45 ` Andreas Schwab
2004-05-15 17:49 ` Luc Teirlinck
2004-05-15 13:51 ` Luc Teirlinck
2004-05-15 18:26 ` Eli Zaretskii
2004-05-15 3:23 ` Luc Teirlinck
2004-05-15 18:02 ` Luc Teirlinck
2004-05-14 21:02 ` Richard Stallman
2004-05-14 2:31 ` Luc Teirlinck
2004-05-14 5:32 ` Luc Teirlinck
2004-05-14 11:36 ` Kai Grossjohann
2004-05-14 12:06 ` David Kastrup
2004-05-14 17:06 ` Stefan Monnier
2004-05-14 17:54 ` David Kastrup
2004-05-14 18:30 ` Stefan Monnier
2004-05-14 19:08 ` Kim F. Storm
2004-05-14 19:26 ` David Kastrup
2004-05-14 20:33 ` Kim F. Storm
2004-05-14 21:00 ` David Kastrup
2004-05-14 21:19 ` Kim F. Storm
2004-05-14 21:33 ` Stefan Monnier
2004-05-14 22:55 ` Kim F. Storm
2004-05-14 23:04 ` Stefan Monnier
2004-05-15 18:33 ` Richard Stallman
2004-05-14 22:11 ` David Kastrup
2004-05-14 22:57 ` Kim F. Storm
2004-05-14 22:47 ` Luc Teirlinck
2004-05-14 23:14 ` Kim F. Storm
2004-05-14 23:38 ` Luc Teirlinck
2004-05-14 22:50 ` Luc Teirlinck
2004-05-14 23:00 ` Luc Teirlinck
2004-05-14 20:40 ` Kai Grossjohann
2004-05-14 23:26 ` David Kastrup
2004-05-15 16:19 ` Kai Grossjohann
2004-05-15 17:01 ` David Kastrup
2004-05-15 17:26 ` Kai Grossjohann
2004-05-15 18:18 ` David Kastrup
2004-05-16 14:11 ` Kai Grossjohann
2004-05-15 18:33 ` Richard Stallman
2004-05-16 14:13 ` Kai Grossjohann
2004-05-17 1:14 ` Luc Teirlinck
2004-05-17 22:58 ` Richard Stallman
2004-05-18 3:44 ` Luc Teirlinck
2004-05-14 20:32 ` Kai Grossjohann
2004-05-14 21:35 ` Michael Albinus
2004-05-15 16:22 ` Kai Grossjohann
2004-05-14 20:29 ` Kai Grossjohann
2004-05-14 21:02 ` Richard Stallman
2004-05-14 0:54 ` Luc Teirlinck
2004-05-14 2:13 ` Luc Teirlinck
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=ud653bne1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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).