all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Help with org related crash on OpenBSD
Date: Tue, 17 Oct 2017 20:32:17 -0400	[thread overview]
Message-ID: <87vajd70tq.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: CAMYmr8z8Dc-Lci4bcmTs4uo--NYW5P==ZAXpPhCZcOXQsJxFuw@mail.gmail.com

Adrian Bradd <adrian.bradd@gmail.com> writes:

> ​Instrumenting 'org-capture' with edebug might be of some assistance. This should at least allow you to step through org-capture and see where emacs is hanging.
>
> HTH
>
> On 13 October 2017 at 12:51, Aaron Bieber <aaron@bolddaemon.com> wrote:
>
>     Hola,
>    
>     I am trying to track down an issue where emacs hangs on OpenBSD when
>     using org-capture. I happens with org 9.1.2 and 8.2.10 in emacs
>     25.3.1.
>    
>     It seems that 3 out of 4 times, emacs completely hangs when adding a
>     Todo. I have tried setting (toggle-debug-on-quit) and
>     (toggle-debug-on-error), but once the hang happens emacs becomes
>     completely unresponsive. The one time that it doesn't hang, it takes
>     around 3 or 4 seconds to actually open up the gtd.org file.

In addition to the edebug suggestion, you might try these two (three?) as well:

If it's emacs that's hanging, then `strace -p <pid>' might give a hint,
although it's probably better to run emacs under gdb as described in

  https://www.gnu.org/software/emacs/manual/html_node/emacs/Checklist.html#Checklist

That can get hairy though.

If it's org-capture that's hanging, then setting debug-on-quit to t and pressing C-g when
you get a hang might give you a backtrace.

-- 
Nick

      reply	other threads:[~2017-10-18  0:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 16:51 Help with org related crash on OpenBSD Aaron Bieber
2017-10-17 23:54 ` Adrian Bradd
2017-10-18  0:32   ` Nick Dokos [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=87vajd70tq.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@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.