From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35429@debbugs.gnu.org
Subject: bug#35429: 27.0.50; Arbitrary xdisp.c related crashes when working with overlay-using packages
Date: Thu, 25 Apr 2019 16:39:29 -0400 [thread overview]
Message-ID: <CAFyQvY0AQ3eW97_==3CgP0dbitxOinJK5ZtyVuBZHvsFyGecGg@mail.gmail.com> (raw)
In-Reply-To: <83r29pygqk.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2612 bytes --]
Hello Eli,
On Thu, Apr 25, 2019, 4:26 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Kaushal Modi <kaushal.modi@gmail.com>
> > Date: Thu, 25 Apr 2019 11:36:27 -0400
> >
> > In the past one-two weeks
>
> 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.
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.
At least for the first 2K characters it
> seems the answer is yes, because:
>
> > #4 0x0000000000584793 in line_number_display_width (w=w@entry=0x89da880,
> width=width@entry=0x7fffffff43dc, pixel_width=pixel_width@entry=0x7fffffff43e0)
> at indent.c:1981
> > startpos = {
> > charpos = 2874,
> > bytepos = 2874
> > }
>
> As you see, the character and the byte positions coincide, which is a
> sign of a plain ASCII buffer text.
>
> So it makes little sense that the assertion is violated, because it is
> called to validate the same character position of 2874:
>
> > #1 0x00000000005a1232 in die (msg=msg@entry=0x680450 "charpos ==
> BYTE_TO_CHAR (bytepos)", file=file@entry=0x67dc6a "xdisp.c",
> line=line@entry=3047) at alloc.c:7221
> > No locals.
> > #2 0x0000000000456b44 in init_iterator (it=it@entry=0x7fffffff3040,
> w=w@entry=0x89da880, charpos=2874, bytepos=<optimized out>,
> row=<optimized out>, base_face_id=base_face_id@entry=DEFAULT_FACE_ID) at
> xdisp.c:3047
>
> So something strange is at work here, and I cannot see what it could
> be, especially with all those "optimized out" variables.
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?
> 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.
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.
Thanks.
Kaushal
>
[-- Attachment #2: Type: text/html, Size: 4533 bytes --]
next prev parent reply other threads:[~2019-04-25 20:39 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 [this message]
2019-04-26 7:17 ` Eli Zaretskii
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='CAFyQvY0AQ3eW97_==3CgP0dbitxOinJK5ZtyVuBZHvsFyGecGg@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=35429@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.