From: Sam Steingold <sds@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: crash in GC
Date: 24 May 2002 16:50:53 -0400 [thread overview]
Message-ID: <sa0znypl176.fsf@glip.premonitia.com> (raw)
In-Reply-To: <E17BJT1-0002qA-00@fencepost.gnu.org>
> * In message <E17BJT1-0002qA-00@fencepost.gnu.org>
> * On the subject of "Re: crash in GC"
> * Sent on Fri, 24 May 2002 14:07:07 -0400
> * Honorable Eli Zaretskii <eliz@gnu.org> writes:
>
> > 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.
okay - what other options are there: is there a way to tell gdb to dump
core so that I can send it to someone interested in the matter?
--
Sam Steingold (http://www.podval.org/~sds) running RedHat7.2 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
Lisp suffers from being twenty or thirty years ahead of time.
next prev parent reply other threads:[~2002-05-24 20:50 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
2002-05-24 20:50 ` Sam Steingold [this message]
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=sa0znypl176.fsf@glip.premonitia.com \
--to=sds@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).