From: Kai Ma <justksqsf@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65060@debbugs.gnu.org
Subject: bug#65060: 29.1.50; display_count_lines segv
Date: Sat, 12 Aug 2023 19:56:27 +0800 [thread overview]
Message-ID: <0F00067E-9020-4AA5-9F00-AB7AF97ED051@gmail.com> (raw)
In-Reply-To: <83msywejpu.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]
> On Aug 12, 2023, at 16:41, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Kai Ma <justksqsf@gmail.com>
>> Date: Sat, 12 Aug 2023 15:28:16 +0800
>> Cc: 65060@debbugs.gnu.org
>>
>>> On Aug 12, 2023, at 14:50, Eli Zaretskii <eliz@gnu.org> wrote:
>>>
>>> Ping! Can you please help me finish investigating this bug by
>>> providing the information I asked for? Armed with that information, I
>>> think I will be able to find a solution.
>>
>> Sorry for the late reply!
>>
>> cursor (before do) = 0x0
>> * GPT_BYTE = 3072
>> * GAP_SIZE = 2000
>> * BEG_ADDR = 0x0
>> * current_buffer->text->beg = 0x0
>>
>> cursor (before memchr) = 0x0
>> * GPT_BYTE = 3072
>> * GAP_SIZE = 2000
>> * BEG_ADDR = 0x0
>> * current_buffer->text->beg = 0x0
>
> Thanks. My guess was correct: the buffer in question was killed.
>
> Could you please try the patch below, and see if it avoids the
> crashes? The patch causes Emacs to signal an error when
> format-mode-line is called for a dead buffer, so if I did this
> correctly, you should see that Emacs no longer crashes, but there are
> error messages about a dead buffer in *Messages*. If this is what
> happens, you should then take this up with the dirvish developers, and
> ask them to avoid calling format-mode-line for a killed buffer.
Thanks! The patch prevents the crash. I will report this to dirvish developers.
[-- Attachment #2: Type: text/html, Size: 8462 bytes --]
next prev parent reply other threads:[~2023-08-12 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 21:41 bug#65060: 29.1.50; display_count_lines segv Kai Ma
2023-08-05 6:24 ` Eli Zaretskii
2023-08-12 6:50 ` Eli Zaretskii
2023-08-12 7:28 ` Kai Ma
2023-08-12 8:41 ` Eli Zaretskii
2023-08-12 11:56 ` Kai Ma [this message]
2023-08-12 12:08 ` Eli Zaretskii
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=0F00067E-9020-4AA5-9F00-AB7AF97ED051@gmail.com \
--to=justksqsf@gmail.com \
--cc=65060@debbugs.gnu.org \
--cc=eliz@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.