From: Alan Third <alan@idiocy.org>
To: "Paul W. Rankin" <hello@paulwrankin.com>
Cc: 38757@debbugs.gnu.org
Subject: bug#38757:
Date: Fri, 27 Dec 2019 12:00:11 +0000 [thread overview]
Message-ID: <m236d6c71w.fsf@breton.holly.idiocy.org> (raw)
In-Reply-To: <c5284bf3-b6fa-4215-9324-70ac88457d0f@www.fastmail.com> (Paul W. Rankin's message of "Fri, 27 Dec 2019 19:56:13 +1000")
"Paul W. Rankin" <hello@paulwrankin.com> writes:
> On Fri, 27 Dec 2019, at 7:47 PM, martin rudalics wrote:
>> >> Please show a backtrace from GDB when Emacs crashes.
>> >>
>> >> Thanks.
>> >
>> > This might be a bit beyond my skillset (i.e. idk what GDB is...)
>>
>> This thread is confusing. Does Emacs crash or doesn't it, given
>
> It is but a journey... with twists and turns....
>
> But yes Emacs crashes. See:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38757#16
>
> The crash is limited to running emacs as a daemon then interfacing with
> emacsclient -nw
It looks to me like this is the same as bug#38564. Robert applied a fix
that sometimes works, but he has a proper fix worked out, he just needs
to finalise it and apply it.
--
Alan Third
next prev parent reply other threads:[~2019-12-27 12:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 2:27 bug#38757: emacs-27; reliably crashes when wrapping visual lines Paul W. Rankin
2019-12-27 6:06 ` bug#38757: Paul W. Rankin
2019-12-27 7:57 ` bug#38757: Eli Zaretskii
2019-12-27 8:04 ` bug#38757: Paul W. Rankin
2019-12-27 9:15 ` bug#38757: Eli Zaretskii
2019-12-27 9:19 ` bug#38757: Paul W. Rankin
2019-12-27 9:47 ` bug#38757: martin rudalics
2019-12-27 9:56 ` bug#38757: Paul W. Rankin
2019-12-27 12:00 ` Alan Third [this message]
2019-12-27 12:44 ` bug#38757: Paul W. Rankin
2019-12-29 21:10 ` bug#38757: Robert Pluim
2019-12-30 1:00 ` bug#38757: Alan Third
2019-12-30 3:21 ` bug#38757: Paul W. Rankin
2019-12-27 10:29 ` bug#38757: emacs-27; reliably crashes when wrapping visual lines Eli Zaretskii
2019-12-27 14:01 ` Eli Zaretskii
2019-12-28 1:00 ` Paul W. Rankin
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=m236d6c71w.fsf@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=38757@debbugs.gnu.org \
--cc=hello@paulwrankin.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.