From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 24368@debbugs.gnu.org
Subject: bug#24368: 25.1; Assertion failure in attach_marker
Date: Mon, 05 Sep 2016 20:52:57 +0300 [thread overview]
Message-ID: <83y436b5dy.fsf@gnu.org> (raw)
In-Reply-To: <57CDAC95.5020308@gmx.at> (message from martin rudalics on Mon, 05 Sep 2016 19:34:13 +0200)
> Date: Mon, 05 Sep 2016 19:34:13 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: 24368@debbugs.gnu.org
>
> > Obviously, the BUF_z vs BUF_Z_BYTE test should be done for the same
> > buffer whose character and byte positions we compare in the
> > assertions.
>
> How? In attach_frame, the buffer where the positions came from is not
> known.
It looks like the callers already take care of that? Or did you find
a case where this is not happening?
> Anyway, I passed an extra boolean to attach_marker to fix that
> and now I get a similar assertion violation in temp_set_point_both.
> This is a can of worms :-(
Sorry, I guess you lost me: what did you try to fix and how?
next prev parent reply other threads:[~2016-09-05 17:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 7:25 bug#24368: 25.1; Assertion failure in attach_marker martin rudalics
2016-09-05 14:30 ` martin rudalics
2016-09-05 14:35 ` martin rudalics
2016-09-05 14:45 ` martin rudalics
2016-09-05 16:26 ` Eli Zaretskii
2016-09-05 15:04 ` martin rudalics
2016-09-05 16:25 ` Eli Zaretskii
2016-09-05 17:34 ` martin rudalics
2016-09-05 17:52 ` Eli Zaretskii [this message]
2016-09-05 17:58 ` martin rudalics
2016-09-05 18:25 ` Eli Zaretskii
2016-09-05 20:28 ` martin rudalics
2016-09-06 6:44 ` martin rudalics
2016-09-06 14:50 ` Noam Postavsky
2016-09-06 15:35 ` martin rudalics
2016-09-06 15:52 ` Eli Zaretskii
2016-09-06 15:08 ` Eli Zaretskii
2016-09-06 16:09 ` martin rudalics
2016-09-06 16:39 ` Eli Zaretskii
2016-09-06 16:50 ` Eli Zaretskii
2016-09-07 14:52 ` martin rudalics
2016-09-07 15:06 ` Eli Zaretskii
2016-09-07 15:19 ` martin rudalics
2016-09-07 15:47 ` Eli Zaretskii
2016-10-07 8:52 ` martin rudalics
2016-09-06 17:28 ` martin rudalics
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y436b5dy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24368@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).