all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Geoff Shannon <geoffpshannon@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Emacs hung, have attached debugger
Date: Fri, 6 Jun 2014 00:42:17 -0700	[thread overview]
Message-ID: <CA+pAvvxgVghGoY7KGt34sXBFEX4rXqDFYftW5aoLQmDxnmjCPg@mail.gmail.com> (raw)
In-Reply-To: <87tx7y3314.fsf@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

I posted compressed versions of the full backtrace to the bug on debbugs.


On Fri, Jun 6, 2014 at 12:33 AM, David Kastrup <dak@gnu.org> wrote:

> There will be likely a lot of repetition here as this sounds like an
> infinite recursion.  Just the end and the start of the traceback (enough
> to recognize the pattern in the middle) should be enough.  The traceback
> will likely be because of stack overflow.
>

Basically the conclusion I came to after examining the backtrace. Before
Glenn
suggested compressing the full content and attaching it, that's what I had
done.

Though of course I didn't think of including the top entries until after
I'd posted the
bottom ones...


> You can use ulimit (see its man page) to limit the available stack space
> in advance: that should allow you to get a backtrace that is reasonably
> short even without manual intervention.  Just be sure that it's not
> bombing out because of a regular operation.
>

Good idea!  Now if only I could reproduce this crash...

Also, sorry if posting about this on emacs-devel was a bit out of place.

-- 
Geoff

Nothing is ever easy.

[-- Attachment #2: Type: text/html, Size: 1846 bytes --]

  reply	other threads:[~2014-06-06  7:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  7:14 Emacs hung, have attached debugger Geoff Shannon
2014-06-06  7:24 ` Glenn Morris
2014-06-06  7:33 ` David Kastrup
2014-06-06  7:42   ` Geoff Shannon [this message]
2014-06-06  7:50 ` 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

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

  git send-email \
    --in-reply-to=CA+pAvvxgVghGoY7KGt34sXBFEX4rXqDFYftW5aoLQmDxnmjCPg@mail.gmail.com \
    --to=geoffpshannon@gmail.com \
    --cc=dak@gnu.org \
    --cc=emacs-devel@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.