unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noah Slater <nslater@tumbolia.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18763@debbugs.gnu.org
Subject: bug#18763: Emacs is segfaulting
Date: Mon, 20 Oct 2014 16:40:22 +0200	[thread overview]
Message-ID: <CA+Y+445j6J95f07CfuHrXWbUB=m6ccf4wSpGBvUBCK-uz4PmAw@mail.gmail.com> (raw)
In-Reply-To: <83egu5edhk.fsf@gnu.org>

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

Okay, I have upgraded. I'll report back if I see any more crashes. Thanks!

On 18 October 2014 15:03, Eli Zaretskii <eliz@gnu.org> wrote:

> > Date: Sat, 18 Oct 2014 14:55:02 +0200
> > From: Noah Slater <nslater@tumbolia.org>
> >
> > I use Emacs with Org mode a lot. And it's been segcrashing a lot
> recently. It
> > segfaults in a number of different ways. Seems non-deterministic to me.
> (i.e.
> > The same action upon startup can cause it to segfault or not segault,
> seemingly
> > at random.)
> >
> > What information do you need to help with this? Is there some command I
> can run
> > that will produce the output you need to understand why it's segfaulting?
> >
> > I am running GNU Emacs 24.4.50.1 on Mac OS X.
>
> That's an old version of the development trunk, please upgrade to the
> latest trunk and see if the problem still exists.
>
> If it does exist on the latest trunk, please report the details using
> "M-x report-emacs-bug RET".
>
> For crashes, it is best to run Emacs under GDB, and when it crashes,
> type "thread apply all bt full" from the GDB prompt; then post the
> results.
>
> Thanks.
>

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

  reply	other threads:[~2014-10-20 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18 12:55 bug#18763: Emacs is segfaulting Noah Slater
2014-10-18 13:03 ` Eli Zaretskii
2014-10-20 14:40   ` Noah Slater [this message]
2015-12-26 16:12     ` Lars Ingebrigtsen
2014-10-18 13:07 ` Jan Djärv

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='CA+Y+445j6J95f07CfuHrXWbUB=m6ccf4wSpGBvUBCK-uz4PmAw@mail.gmail.com' \
    --to=nslater@tumbolia.org \
    --cc=18763@debbugs.gnu.org \
    --cc=eliz@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).