unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Fatal error (6).Aborted (core dumped)
Date: Thu, 21 Mar 2002 08:45:20 +0200 (IST)	[thread overview]
Message-ID: <Pine.SUN.3.91.1020321084223.5863L-100000@is> (raw)
In-Reply-To: <m3u1rbkvma.fsf@micawber.queens.ox.ac.uk>


On 20 Mar 2002, Anthony Goreham wrote:

> Emacs dies with the above message every time I run it on the console.
> It still works OK under X.  I am using Emacs 21.2 on RedHat Linux
> (version 7.0 with some updates).

Thank you for your report.

> I have found the problem goes away in either of the following cases:
> 
> 1.  If I comment out anything in my .emacs that might cause emacs to
>     use highlighting (font-lock-mode, show-paren-mode, transient-mark-mode).

What happens if you invoke Emacs with "emacs -q --no-site-file", and then 
turn on these highlighting features from within Emacs?  What happens if 
you evaluate the customizations in your .emacs from a running session 
invoked as mentioned above?

> Is this a bug in emacs, or a problem in my system setup?
> Can anyone give me a clue about what needs fixing?

It's hard to tell without more information.

> In case it helps, here's what I get when I run "gdb emacs core":

It doesn't help, unfortunately, since your binary appears to be stripped 
(no debug info), so the debugger cannot tell anything interesting.  Can 
you produce a backtrace from an unstripped binary?

_______________________________________________
Bug-gnu-emacs mailing list
Bug-gnu-emacs@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs


       reply	other threads:[~2002-03-21  6:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3u1rbkvma.fsf@micawber.queens.ox.ac.uk>
2002-03-21  6:45 ` Eli Zaretskii [this message]
2002-03-21 10:26   ` Fatal error (6).Aborted (core dumped) Anthony Goreham
2002-03-21 11:06     ` 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=Pine.SUN.3.91.1020321084223.5863L-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=bug-gnu-emacs@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).