unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Doug Lewan <dougl@shubertticketing.com>
To: "blacknwhite77@gmail.com" <blacknwhite77@gmail.com>,
	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: Random bus error
Date: Fri, 9 Jan 2015 13:50:19 +0000	[thread overview]
Message-ID: <155DEC68569B714B86C2C7075F5EDA9892BBCA57@DAKIYA1.pegasus.local> (raw)
In-Reply-To: <c2f15e3e-1540-45cd-b66f-a3202d9e3d63@googlegroups.com>

A few things come to mind right away.

1. Run emacs -Q to get a pure, minimal emacs. 
   If that crashes, then it is indeed an issue restricted to emacs. (And see point 2.)
You probably still want your customizations, so
2. Run emacs under a debugger. 
   When there's a crash grab whatever stack information you can. 
   In gdb(1GNU) the magic incantation is `thread apply all bt'.
   Your debugger may be different.
3. (setq debug-on-error t) will show you certain extreme errors in your non-optimized .emacs.
   They may not be the immediate source of the crash, 
   but fixing them will eliminate distracting failures.

Hope this helps.

-- 
,Doug
Douglas Lewan
Shubert Ticketing
(201) 489-8600 ext 224 or ext 4335

"This is a slow pup," he said continuing his ascent.


> -----Original Message-----
> On
> Behalf Of blacknwhite77
> Subject: Random bus error
> 
> Every couple of days, unexpectedly and without any specific trigger
> emacs crashes with bus error message in terminal. I have an elaborate
> "non optimized" .emacs file.
> How should I go about debugging the issue?
> 
> I am using GNU Emacs 24.3.1, on Solaris operating system. GNU Emacs
> 24.3.1 (sparc-sun-solaris2.10, GTK+ Version 2.10.13)



  reply	other threads:[~2015-01-09 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09  7:41 Random bus error blacknwhite77
2015-01-09 13:50 ` Doug Lewan [this message]
     [not found] ` <mailman.17524.1420811425.1147.help-gnu-emacs@gnu.org>
2015-01-09 18:14   ` blacknwhite77
2015-01-10  6:10     ` Alexis

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=155DEC68569B714B86C2C7075F5EDA9892BBCA57@DAKIYA1.pegasus.local \
    --to=dougl@shubertticketing.com \
    --cc=blacknwhite77@gmail.com \
    --cc=help-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.
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).