all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alexis <flexibeast@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Random bus error
Date: Sat, 10 Jan 2015 17:10:42 +1100	[thread overview]
Message-ID: <877fwvqi71.fsf@gmail.com> (raw)
In-Reply-To: <e2de2867-2e01-4290-92ce-5f41480bc44a@googlegroups.com>


blacknwhite77@gmail.com writes:

> 2. I have very little knowledge of emacs debugger. Is there
> documentation somewhere on how to run emacs under a debugger?

See the file etc/DEBUG.

> Also, as I mentioned earlier, this crash is very random and nothing in
> specific triggers it, so I am not sure how running under a debugger
> might help.

Running Emacs under e.g. gdb can allow one to query for information
about the call stack, values of various variables etc. immediately after
the crash has happened, and before such information is irretrievably
lost.

> 3. This seems to be the closest to what might help. I did set the
> debug-on-error value in my .emacs, but my question is once the app
> crashes where do I find the crash log?

`debug-on-error` is more for debugging Emacs Lisp, presenting
debugging-related information in a new buffer whilst Emacs is still
running. App crashes are probably more likely to be occurring at the C
level, hence the need to run Emacs under a C debugger such as gdb - as
distinct from using the ELisp debugging facilities built-in to Emacs
(e.g. EDebug), which one uses from within Emacs itself.


Alexis.



      reply	other threads:[~2015-01-10  6:10 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
     [not found] ` <mailman.17524.1420811425.1147.help-gnu-emacs@gnu.org>
2015-01-09 18:14   ` blacknwhite77
2015-01-10  6:10     ` Alexis [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877fwvqi71.fsf@gmail.com \
    --to=flexibeast@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.