From: Doug Lewan <dougl@shubertticketing.com>
To: Noah Slater <nslater@apache.org>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Getting lots of Emacs crashes
Date: Wed, 3 Sep 2014 13:53:01 +0000 [thread overview]
Message-ID: <155DEC68569B714B86C2C7075F5EDA9892B1A9AA@DAKIYA1.pegasus.local> (raw)
In-Reply-To: <CAPaJBx6oh3PsvyEvvEt2Yapr0jY_98mXEBsYpT8rWovECoTwUA@mail.gmail.com>
> -----Original Message-----
> Behalf Of Noah Slater
> Sent: Monday, 2014 September 01 16:06
> To: emacs-orgmode
> Subject: [O] Getting lots of Emacs crashes
>
> Hello,
>
> I'm getting a lot of Emacs crashes recently using Org. Is there any
> way I can help to debug why this is happening?
Noah,
You might consider running emacs under a debugger. It will trap the crash and then you can ask where it happened, i.e. a stack trace. The information might be of more interest to an emacs developer than to you.
GNU software should not crash. From the emacs info (a description of a typical crash):
If Emacs accesses an invalid memory location ("segmentation fault"), or
exits with an operating system error message that indicates a problem
in the program (as opposed to something like "disk full"), then it is
certainly a bug.
The stack trace (along with all the other information that belongs in a bug report) can be very helpful.
,Doug
Douglas Lewan
Shubert Ticketing
(201) 489-8600 ext 224 or ext 4335
"This is a slow pup," he said continuing his ascent.
next prev parent reply other threads:[~2014-09-03 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 20:06 Getting lots of Emacs crashes Noah Slater
2014-09-02 15:12 ` Richard Lawrence
2014-09-02 21:52 ` David Arroyo Menendez
2014-09-03 6:59 ` Thorsten Jolitz
2014-09-03 13:53 ` Doug Lewan [this message]
2014-10-05 18:43 ` Noah Slater
2014-10-13 15:36 ` Noah Slater
2014-10-13 15:54 ` Nicolas Goaziou
2014-10-21 14:35 ` Noah Slater
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=155DEC68569B714B86C2C7075F5EDA9892B1A9AA@DAKIYA1.pegasus.local \
--to=dougl@shubertticketing.com \
--cc=emacs-orgmode@gnu.org \
--cc=nslater@apache.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/org-mode.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).