unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: 17269@debbugs.gnu.org
Subject: bug#17269: 24.3.90; assertion failure at buf_charpos_to_bytepos (marker.c)
Date: Tue, 15 Apr 2014 18:53:26 +0300	[thread overview]
Message-ID: <83r44yk2rt.fsf@gnu.org> (raw)
In-Reply-To: <87eh0y3bvz.fsf@geodiff-mac3.ulb.ac.be>

> From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
> Date: Tue, 15 Apr 2014 16:28:32 +0200
> 
> I got this today (I was running without --enable-checking until today).
> 
> I still have that session open in case you want more info.
> 
> Also, as a side note, in the current buffer (in which I'm reporting the
> bug), I see problems like <end> going five to 5 to 10 lines below
> current position. Apparently, it happens after I use C-k (kill-line). It
> goes way when setting (setq cache-long-line-scans nil). I guess the
> crash and this problem are related ?

It's related, but can you reproduce this in "emacs -Q"?

> I'm running emacs-24 branch at commit
> ef5b917 * savannah/emacs-24 Fix relative links to parent directories in shr
> *but* I also have applied Paul Eggert's patch mentionned in bug#17172

Not sure what this means, Paul made several commits during the last 2
days.  Can you be more specific (or even state the bzr revision
number)?

> Breakpoint 1, terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:351
> 351	  signal (sig, SIG_DFL);
> #0  terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:351
> #1  0x081f581f in die (msg=0x83079dc "BUF_BEG (b) <= charpos && charpos <= BUF_Z (b)", file=0x83079d0 "marker.c", line=145) at alloc.c:6826
> #2  0x081bc08d in buf_charpos_to_bytepos (b=0x9b42080, charpos=14233) at marker.c:145
> #3  0x081d7c59 in find_newline (start=14230, start_byte=14230, end=14231, end_byte=14231, count=1, shortage=0xbfffdcd4, bytepos=0x0, allow_quit=true) at search.c:780
> #4  0x081d845f in find_before_next_newline (from=14224, to=0, cnt=1, bytepos=0x0) at search.c:1006
> #5  0x082019e6 in Fline_end_position (n=4) at editfns.c:813
> #6  0x081ceff0 in Fend_of_line (n=4) at cmds.c:199

What is the value of BUF_Z(b) in frame #2?

Also, what is the major mode in the buffer in question?





  reply	other threads:[~2014-04-15 15:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 14:28 bug#17269: 24.3.90; assertion failure at buf_charpos_to_bytepos (marker.c) Nicolas Richard
2014-04-15 15:53 ` Eli Zaretskii [this message]
2014-04-15 16:11   ` Nicolas Richard
2014-04-15 18:11     ` Eli Zaretskii
2014-04-15 18:35       ` Nicolas Richard
2014-04-15 20:45       ` Nicolas Richard
2014-04-16  5:44         ` Eli Zaretskii
2014-04-16  6:57           ` Dmitry Antipov
2014-04-16  7:24             ` Eli Zaretskii
2014-04-17  7:29           ` Eli Zaretskii
2014-04-17 10:14             ` Nicolas Richard
2014-04-17 10:20               ` 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

  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=83r44yk2rt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17269@debbugs.gnu.org \
    --cc=theonewiththeevillook@yahoo.fr \
    /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).