unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: unpredictable emacs 21 crashes
Date: Sat, 15 Jun 2002 08:14:00 -0600 (MDT)	[thread overview]
Message-ID: <200206151414.g5FEE0G10343@aztec.santafe.edu> (raw)
In-Reply-To: <xkk7p6kap2.fsf@maxwell.astro.utoronto.ca> (message from Rob Reid on Mon, 10 Jun 2002 22:53:13 GMT)

    (gdb) up
    #1  0x80d6044 in fatal_error_signal ()
    (gdb) up
    #2  <signal handler called>
    (gdb) up
    #3  0x811d476 in mark_object ()
    (gdb) up

This is a failure in GC.  It is natural that there would be many stack
frames recursively calling mark_object.  To find where GC was called,
try moving up the stack many frames at once.  Use `up 100' for
instance.  Try various numbers; do a binary search.

Most likely, whatever called GC won't be relevant.
The crash is probably due to invalid data.  To analyze it
you need to study the data being worked on in the innermost frames.
By working back one frame at a time, you can see what data structure
the invalid objects are found in.  The vector last_marked (see
alloc.c) can help you trace this back.

Once you see if there is a pattern to that, we might have an idea
where to look for the real problem.

This analysis process is nontrivial, but there's no shortcut
except to be very very lucky.

       reply	other threads:[~2002-06-15 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <xkk7p6kap2.fsf@maxwell.astro.utoronto.ca>
2002-06-15 14:14 ` Richard Stallman [this message]
2002-06-16  5:43   ` unpredictable emacs 21 crashes Eli Zaretskii

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=200206151414.g5FEE0G10343@aztec.santafe.edu \
    --to=rms@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).