all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Marc Munro <marc@bloodnok.com>
Cc: 29726-done@debbugs.gnu.org
Subject: bug#29726: 25.1; SIGSEGV in find-file
Date: Sun, 24 Dec 2017 05:21:36 +0200	[thread overview]
Message-ID: <83h8sgkdz3.fsf@gnu.org> (raw)
In-Reply-To: <1514063141.3545.7.camel@bloodnok.com> (message from Marc Munro on Sat, 23 Dec 2017 13:05:41 -0800)

> From: Marc Munro <marc@bloodnok.com>
> Cc: 29726@debbugs.gnu.org
> Date: Sat, 23 Dec 2017 13:05:41 -0800
> 
> On Sat, 2017-12-23 at 14:07 +0200, Eli Zaretskii wrote:
> > > Date: Sun, 17 Dec 2017 19:23:32 +0200
> > > From: Eli Zaretskii <eliz@gnu.org>
> > [ . . . ]
> > I installed a protection against such calamities in the emacs-26
> > branch, which displays a backtrace with an error message instead of
> > crashing.  If you can build the Emacs's emacs-26 release branch,
> > please do and see that the crashes are gone.
> 
> Eli,
> Thank you so much.  Yes, that has eliminated the crash.  Now I just
> have to make my code do something sane.
> 
> You can close the bug, if you haven't already.

Thanks, closing.





  reply	other threads:[~2017-12-24  3:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 21:48 bug#29726: 25.1; SIGSEGV in find-file Marc Munro
2017-12-16  9:35 ` Eli Zaretskii
2017-12-16 19:43   ` Marc Munro
2017-12-16 20:07     ` Eli Zaretskii
2017-12-16 20:31       ` Marc Munro
2017-12-16 20:35         ` Marc Munro
2017-12-16 20:48         ` Eli Zaretskii
     [not found]           ` <1513457838.13815.40.camel@bloodnok.com>
2017-12-17 17:23             ` Eli Zaretskii
2017-12-17 19:27               ` Marc Munro
2017-12-23 12:07               ` Eli Zaretskii
2017-12-23 21:05                 ` Marc Munro
2017-12-24  3:21                   ` Eli Zaretskii [this message]
2017-12-16 20:44       ` Marc Munro
2017-12-16 20:56         ` Eli Zaretskii
2017-12-16  9:42 ` martin rudalics

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=83h8sgkdz3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29726-done@debbugs.gnu.org \
    --cc=marc@bloodnok.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.