all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Joseph Mingrone <jrm@ftfl.ca>
Cc: Glenn Morris <rgm@gnu.org>, 18411@debbugs.gnu.org
Subject: bug#18411: new coredump
Date: Wed, 09 Sep 2020 14:32:01 +0200	[thread overview]
Message-ID: <875z8nb072.fsf@gnus.org> (raw)
In-Reply-To: <86y2lj9lqh.fsf@phe.ftfl.ca> (Joseph Mingrone's message of "Wed,  09 Sep 2020 09:29:42 -0300")

Joseph Mingrone <jrm@ftfl.ca> writes:

> On Wed, 2020-09-09 at 11:52, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>> This was four years ago, but there was unfortunately no follow-up on
>> this at the time.
>
>> Are you still seeing these segfaults with the current version of Emacs?
>
> No, I'm no longer seeing these regular segfaults.

OK, closing this bug report.  Please respond to the debbugs address if
the problem reoccurs, and we'll reopen the report.

> But, I'm mostly running master-branch snapshots no more than two weeks
> old (to test the FreeBSD packages).

Even better.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2020-09-09 12:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 15:39 bug#18411: 24.3; Emacs (daemon) core dumps after save-buffers-kill-terminal Joseph Mingrone
2014-09-05 16:08 ` bug#18411: No .gbdinit file in src/ directory Joseph Mingrone
2014-09-05 16:18   ` Glenn Morris
2014-09-05 16:47     ` Joseph Mingrone
2014-09-05 17:55       ` Eli Zaretskii
2014-09-08 15:08 ` bug#18411: new coredump Joseph Mingrone
2014-09-08 15:50   ` Glenn Morris
2014-09-08 16:10     ` Joseph Mingrone
2015-09-13 16:27 ` Joseph Mingrone
2020-09-09  9:52   ` Lars Ingebrigtsen
2020-09-09 12:29     ` Joseph Mingrone
2020-09-09 12:32       ` Lars Ingebrigtsen [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=875z8nb072.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=18411@debbugs.gnu.org \
    --cc=jrm@ftfl.ca \
    --cc=rgm@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.