From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: jguenther@gmail.com, 39164@debbugs.gnu.org
Subject: bug#39164: 27.0.60; Intermittent crash on MacOS 10.14 in setup_process_coding_systems
Date: Mon, 20 Jan 2020 20:00:49 +0200 [thread overview]
Message-ID: <83y2u2vwha.fsf@gnu.org> (raw)
In-Reply-To: <m2eevutrnz.fsf@gmail.com> (message from Robert Pluim on Mon, 20 Jan 2020 10:15:28 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Justin Guenther <jguenther@gmail.com>, 39164@debbugs.gnu.org
> Date: Mon, 20 Jan 2020 10:15:28 +0100
>
> >>>>> On Fri, 17 Jan 2020 23:01:10 +0200, Eli Zaretskii <eliz@gnu.org> said:
>
> Eli> Thanks, but the backtraces don't show any source information, and it
> Eli> is very hard to do anything about this without that. Can you tell
> Eli> where in coding.c is setup_process_coding_systems + 152?
>
> Iʼm on 10.14, and donʼt see this crash. Assuming my emacs-27 build is
> similar to Justin's, itʼs this:
>
> 7988 setup_coding_system (coding_system, proc_decode_coding_system[inch]);
> 0x000000010019645f <+143>: mov (%r12,%r15,8),%rsi
> 0x0000000100196463 <+147>: callq 0x10007b610 <setup_coding_system>
>
> 7989
> 7990 if (!proc_encode_coding_system[outch])
> 0x0000000100196468 <+152>: lea 0x4d3061(%rip),%r15 # 0x1006694d0
> 0x000000010019646f <+159>: mov (%r15,%r14,8),%rsi
> 0x0000000100196473 <+163>: test %rsi,%rsi
> 0x0000000100196476 <+166>: jne 0x100196489 <setup_process_coding_systems+185>
Does this mean proc_encode_coding_system is NULL (or garbled), or the
value of outch is outlandish (or garbled)? Showing the values of
these variables will be appreciated.
next prev parent reply other threads:[~2020-01-20 18:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 19:00 bug#39164: 27.0.60; Intermittent crash on MacOS 10.14 in setup_process_coding_systems Justin Guenther
2020-01-17 21:01 ` Eli Zaretskii
2020-01-20 9:15 ` Robert Pluim
2020-01-20 18:00 ` Eli Zaretskii [this message]
2020-01-20 18:42 ` Robert Pluim
2020-01-27 13:26 ` mituharu
2020-01-27 18:19 ` Eli Zaretskii
2020-01-28 7:59 ` Robert Pluim
2020-01-28 8:23 ` YAMAMOTO Mitsuharu
2020-01-28 8:41 ` Robert Pluim
2020-01-28 9:02 ` Eli Zaretskii
2020-01-28 9:14 ` YAMAMOTO Mitsuharu
2020-01-28 9:42 ` Eli Zaretskii
2020-01-28 10:06 ` YAMAMOTO Mitsuharu
2020-01-28 17:37 ` Eli Zaretskii
2020-01-29 10:26 ` YAMAMOTO Mitsuharu
2020-01-29 11:09 ` Eli Zaretskii
2020-01-29 12:38 ` Eli Zaretskii
2020-01-30 9:42 ` YAMAMOTO Mitsuharu
2020-01-30 14:49 ` Eli Zaretskii
2020-01-26 17:41 ` bug#39164: Reproducing SIGSEGV bug Tomasz Kowal
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=83y2u2vwha.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39164@debbugs.gnu.org \
--cc=jguenther@gmail.com \
--cc=rpluim@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.