unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs crashes
Date: Tue, 14 Mar 2006 06:33:09 +0200	[thread overview]
Message-ID: <upskptzlm.fsf@gnu.org> (raw)
In-Reply-To: <17429.54459.803236.351040@kahikatea.snap.net.nz> (message from Nick Roberts on Tue, 14 Mar 2006 09:23:23 +1300)

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Tue, 14 Mar 2006 09:23:23 +1300
> 
> 1) It hangs with some kind of mutex lock which I don't understand with a brief
>    backtrace of three functions in libc, I think.  The only thing I can do,
>    after attaching with GDB, is kill it.

Please show at least that short backtrace.

> 2) A garbage collection related crash where mark_object is called recursively 
>    literally thousands of times,

The fact that there are thousands of recursive calls to mark_object is
not in itself a sign of a problem.  It is normal for the mark phase to
be deeply recursive.

etc/DEBUG has some text on how to debug crashes during GC.  Could you
try to use those techniques and see what data structure is corrupted?

  parent reply	other threads:[~2006-03-14  4:33 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13 20:23 Emacs crashes Nick Roberts
2006-03-13 20:47 ` Chong Yidong
2006-03-13 22:06 ` Kim F. Storm
2006-03-14  0:39   ` Kenichi Handa
2006-03-14 16:09     ` Richard Stallman
2006-03-15  3:24       ` Giorgos Keramidas
2006-03-15 20:23         ` Richard Stallman
2006-03-14  1:02   ` Juanma Barranquero
2006-03-14  9:36     ` David Kastrup
2006-03-14 11:59       ` Juanma Barranquero
2006-03-14 17:45         ` Richard Stallman
2006-03-15  8:58           ` Juanma Barranquero
2006-03-17 16:32             ` Richard Stallman
2006-03-17 16:41               ` Juanma Barranquero
2006-03-14  1:37   ` Nick Roberts
2006-03-14 16:07   ` Chong Yidong
2006-03-14 16:15     ` Kim F. Storm
2006-03-14 16:09   ` Richard Stallman
2006-03-14 20:47     ` Kim F. Storm
2006-03-14 21:35       ` Chong Yidong
2006-03-15 20:21         ` Richard Stallman
2006-03-14 22:38       ` Kim F. Storm
2006-03-15  9:22         ` Nick Roberts
2006-03-15  9:28           ` David Kastrup
2006-03-15 11:35           ` Jan D.
2006-03-15  3:21       ` Giorgos Keramidas
2006-03-15 20:21       ` Richard Stallman
2006-03-15 15:41     ` Kim F. Storm
2006-03-15 17:05       ` Luc Teirlinck
2006-03-15 17:21       ` Chong Yidong
2006-03-15 19:03       ` Kim F. Storm
2006-03-15 21:40         ` Nick Roberts
2006-03-14  4:33 ` Eli Zaretskii [this message]
2006-03-14 20:45   ` Nick Roberts
2006-03-15  4:43     ` Eli Zaretskii
2006-03-15  7:49       ` Nick Roberts
2006-03-15 19:49         ` Eli Zaretskii
2006-03-15 21:40           ` Nick Roberts
2006-03-16 20:18             ` Richard Stallman
2006-03-16 21:25               ` Nick Roberts
2006-03-18 14:31                 ` Eli Zaretskii
2006-03-15 20:21     ` Richard Stallman
2006-03-16 20:18       ` Richard Stallman

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=upskptzlm.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).