all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vin Shelton <ethersoft@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 19314@debbugs.gnu.org
Subject: bug#19314: 25.0.50; Core Dump on Mint 17.1
Date: Fri, 15 Jun 2018 07:37:00 -0400	[thread overview]
Message-ID: <CACeGjnUJ4y6VE08r6pOQJEKN=6FY3VCduwPg5ntETDnXaDAh-Q@mail.gmail.com> (raw)
In-Reply-To: <87tvq4uvw5.fsf@gmail.com>

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

I can't even remember writing that message.

I have not seen emacs crashes at all recently (for approximately the last
year, at least).

  - Vin

On Fri, Jun 15, 2018 at 7:33 AM, Noam Postavsky <npostavs@gmail.com> wrote:

> Vin Shelton <ethersoft@gmail.com> writes:
>
> > Dear Maintainers,
> >
> > Ever since updating to linux Mint 17.1,  I have been getting emacs has
> > been dumping core every couple of days.  I rebuilt with symbols
> > enabled and you will find the backtrace below.  The emacs is sitting
> > idle, typically while the computer is idling with the screen blanked.
> > I think the crashes has something to do with threads; I would not be
> > surprised to find that the error occurs in the libpthread or libc, but
> > I wanted to notify you of the failure in case it is actually
> > emacs-related.
> >
> > Please let me know if there is any further information you need.
>
> Sorry nobody followed up with this at the time.  There have been quite a
> few fixes since then, is this still a problem with more recent Emacs
> versions, 25.3 or 26.1?
>

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

  reply	other threads:[~2018-06-15 11:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 19:01 bug#19314: 25.0.50; Core Dump on Mint 17.1 Vin Shelton
2018-06-15 11:33 ` Noam Postavsky
2018-06-15 11:37   ` Vin Shelton [this message]
2018-06-15 11:52     ` Noam Postavsky

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='CACeGjnUJ4y6VE08r6pOQJEKN=6FY3VCduwPg5ntETDnXaDAh-Q@mail.gmail.com' \
    --to=ethersoft@gmail.com \
    --cc=19314@debbugs.gnu.org \
    --cc=acs@alumni.princeton.edu \
    --cc=npostavs@gmail.com \
    /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.