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 21:11:45 +0300 [thread overview]
Message-ID: <83ob02jwda.fsf@gnu.org> (raw)
In-Reply-To: <534D5A4F.8050000@yahoo.fr>
> Date: Tue, 15 Apr 2014 18:11:59 +0200
> From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
> CC: 17269@debbugs.gnu.org
>
> > It's related, but can you reproduce this in "emacs -Q"?
>
> Not yet, but it seems to be triggered by the bug report because it just happened again. I'll look at it later. I have to run now.
Thanks.
> > What is the value of BUF_Z(b) in frame #2?
>
> (gdb) f 2
> #2 0x081bc08d in buf_charpos_to_bytepos (b=0x9b42080, charpos=14233) at marker.c:145
> 145 eassert (BUF_BEG (b) <= charpos && charpos <= BUF_Z (b));
> (gdb) p BUF_Z(b)
> $1 = 14231
> (gdb) xpr
> Lisp_Float
> Cannot access memory at address 0x3790
>
> Perhaps I'm using the wrong command ?
No, you just don't need xpr, 14231 is a simple number.
> > Also, what is the major mode in the buffer in question?
>
> Could you tell me how to find out with gdb ?
(gdb) p b->name_
(gdb) xstring
This will print the name of the buffer, which should be enough for you
to know its major mode.
next prev parent reply other threads:[~2014-04-15 18:11 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
2014-04-15 16:11 ` Nicolas Richard
2014-04-15 18:11 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ob02jwda.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 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.