From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 35429@debbugs.gnu.org
Subject: bug#35429: 27.0.50; Arbitrary xdisp.c related crashes when working with overlay-using packages
Date: Fri, 26 Apr 2019 10:17:59 +0300 [thread overview]
Message-ID: <83ef5pxmjc.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY0AQ3eW97_==3CgP0dbitxOinJK5ZtyVuBZHvsFyGecGg@mail.gmail.com> (message from Kaushal Modi on Thu, 25 Apr 2019 16:39:29 -0400)
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Thu, 25 Apr 2019 16:39:29 -0400
> Cc: 35429@debbugs.gnu.org
>
> Any chance for a more accurate time frame? Or maybe even bisection?
>
> Sorry, I don't have a to consistent way to reproduce this. But I have noticed that no crash has happened since
> I disabled the beacon package.
I doubt that the beacon package is where the bug is, so I was asking
whether a previous version of master didn't have this problem. Or are
you saying that you only started using the beacon package a few weeks
ago?
> Thanks. Unfortunately, the backtrace makes no sense to me. The
> buffer was pure ASCII, right?
>
> If you mean the presence of Unicode characters, then I have the unicode box drawing characters too. The Org
> file content is not 100% 8-bit ASCII.
Not even its first 2874 characters?
Are the box drawing characters part of buffer text, or are they
displayed via overlays and display properties?
> This time, I enabled logging to a file as there was no way I would be able to copy all that info screen by screen
> into the email. Does that option optimize out certain variables?
No.
> I would suggest to try an unoptimized build,
>
> Hmm, I am already building Emacs with your suggested switches of -ggdb3 and -Og (from an earlier gdb
> debug in a different thread). Let me know if a different set of switches are needed.
By "unoptimized" I mean '-O0 -ggdb3'. -Og still optimizes, it just
avoids optimizations that make debugging exceptionally hard.
> and if the same crashes
> happen there as well, perhaps the backtrace will tell something more
> useful. It would help to know the value of bytepos argument to
> init_iterator, and if it indeed is equal to charpos, the next thing to
> look at is the buffer's markers.
>
> I still have the gdb session alive if you want me to run some debug commands for you.
What are the values of these:
(gdb) p current_buffer->pt
(gdb) p current_buffer->pt_byte
(gdb) p current_buffer->text->gpt
(gdb) p current_buffer->text->gpt_byte
(gdb) p current_buffer->begv
(gdb) p current_buffer->begv_byte
(gdb) p current_buffer->zv
(gdb) p current_buffer->zv_byte
next prev parent reply other threads:[~2019-04-26 7:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 15:36 bug#35429: 27.0.50; Arbitrary xdisp.c related crashes when working with overlay-using packages Kaushal Modi
2019-04-25 20:25 ` Eli Zaretskii
2019-04-25 20:39 ` Kaushal Modi
2019-04-26 7:17 ` Eli Zaretskii [this message]
2019-04-26 14:08 ` Kaushal Modi
2019-04-26 18:08 ` Eli Zaretskii
2019-04-26 18:22 ` Kaushal Modi
2019-04-26 18:32 ` Eli Zaretskii
2019-04-26 18:34 ` Kaushal Modi
2019-04-26 19:04 ` Eli Zaretskii
2019-04-26 19:12 ` Kaushal Modi
2019-04-26 19:25 ` Eli Zaretskii
2019-04-26 19:39 ` Kaushal Modi
2019-04-26 19:43 ` Eli Zaretskii
2019-05-01 15:45 ` Kaushal Modi
2019-05-01 17:19 ` Eli Zaretskii
2019-04-26 19:43 ` Kaushal Modi
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=83ef5pxmjc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35429@debbugs.gnu.org \
--cc=kaushal.modi@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.