[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#35253: emacs-27.0.50_2019-01-17; `-nw' option causes core dump
From: |
Eli Zaretskii |
Subject: |
bug#35253: emacs-27.0.50_2019-01-17; `-nw' option causes core dump |
Date: |
Sat, 13 Apr 2019 12:31:14 +0300 |
> From: Atsuo Ohki <ohki1701g@gmail.com>
> Cc: Atsuo Ohki <ohki1701g@gmail.com>
> Comments: In-reply-to Eli Zaretskii <eliz@gnu.org>
> message dated "Sat, 13 Apr 2019 09:41:11 +0300."
> Date: Sat, 13 Apr 2019 17:32:10 +0900
>
> > Also, does "_2019-01-17" above mean that this is a Jan 2019 snapshot
> > of the development sources? Because I think this problem was already
> > reported and fixed since then, with this fragment at the end of
> > coding.c in the current sources:
> >
> > /* In temacs the below is done by mule-conf.el, because we need to
> > define us-ascii first. But in dumped Emacs us-ascii is restored
> > by the above loop, and mule-conf.el will not be loaded, so we set
> > it up now; otherwise safe_terminal_coding will remain zeroed. */
> > Fset_safe_terminal_coding_system_internal (Qus_ascii);
>
> Thank you for an action.
>
> As you guess, I used a Jan 2019 snapshot of the development sources
> got from http://alpha.gnu.org/gnu/emacs/pretest.
>
> A segmentation fault occurs in the function `encode_coding()',
> when refering `coding->encoder' (`coding' is null at that point).
>
> So, I'm sure my bug report has already fixed.
Thanks, I'm therefore closing this bug report.