From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: crash in GC
Date: Fri, 24 May 2002 14:07:07 -0400 [thread overview]
Message-ID: <E17BJT1-0002qA-00@fencepost.gnu.org> (raw)
In-Reply-To: <sa0lma9ocgf.fsf@glip.premonitia.com> (message from Sam Steingold on 24 May 2002 10:19:28 -0400)
> From: Sam Steingold <sds@gnu.org>
> Date: 24 May 2002 10:19:28 -0400
>
> > Could you investigate a little further and try to find the data that
> > is invalid or inconsistent?
>
> I am afraid not. All I have is the backtrace.
> (I restarted Emacs in the same gdb since I need it for other work.)
That is very unfortunate: it means that this bug report cannot be
pursued at all. Please in the future try to leave the crashed session
running as long as the thread that discusses the crash is alive. If
you can afford that resourcewise, that is.
Crashes inside GC generally mean that some memory corruption happened
earlier, but the backtrace doesn't say where and when. It is
impossible to debug such problems armed with the backtrace alone; you
need to examine the relevant C and Lisp data structures, and you need
to check several hypotheses about the possible cause(s) of the
corruption. You can't even start thinking about these issues without
knowing the extent of data structures that are corrupted, and without
access to the array that records the GC history.
next prev parent reply other threads:[~2002-05-24 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 19:06 crash in GC Sam Steingold
2002-05-24 0:44 ` Richard Stallman
2002-05-24 14:19 ` Sam Steingold
2002-05-24 18:07 ` Eli Zaretskii [this message]
2002-05-24 20:50 ` Sam Steingold
2002-05-25 1:04 ` Ken Raeburn
2002-05-25 8:26 ` Eli Zaretskii
2002-05-25 21:20 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-12-15 20:17 Sam Steingold
2002-12-19 18:33 ` 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=E17BJT1-0002qA-00@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=eliz@is.elta.co.il \
--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).