From: "Juanma Barranquero" <lekktu@gmail.com>
To: 874@emacsbugs.donarmstrong.com
Subject: bug#874: Args out of range with new auto-composition implementation
Date: Thu, 4 Sep 2008 17:25:46 +0200 [thread overview]
Message-ID: <f7ccd24b0809040825h29f4a1etd2c70a4098fb865@mail.gmail.com> (raw)
In-Reply-To: <f7ccd24b0809030921q643779e8t28aae7d9cf1b6d44@mail.gmail.com>
On Wed, Sep 3, 2008 at 18:21, Juanma Barranquero <lekktu@gmail.com> wrote:
> emacs -Q -l testbug.el
> C-h H
> M-: (goto-char 276) <RET> ;; or move the cursor to any auto-composed char
> M-x testbug <RET>
>
> => "Args out of range: 274, 274"
Curious. The out of range error is caused by this code in
textprop.c:validate_interval_range
if (!(BUF_BEGV (b) <= XINT (*begin) && XINT (*begin) <= XINT (*end)
&& XINT (*end) <= BUF_ZV (b)))
args_out_of_range (*begin, *end);
At that point,
BUF_BEGV (b) = 1
BUF_ZV (b) = 1
XINT (*begin) = 274
XINT (*end) = 274
where *begin and *end point to the position in buffer "HELLO", but b
(and hence object, from which b is extracted) points to the just
created buffer "testbug":
(gdb) p object
$1 = 64949764
(gdb) xbuffer
$2 = (struct buffer *) 0x3df0e00
(unsigned char *) 0x3de6880 "testbug"
so it's no wonder it fails.
next prev parent reply other threads:[~2008-09-04 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 23:39 Args out of range with new auto-composition implementation Juanma Barranquero
2008-09-11 2:07 ` Kenichi Handa
2008-09-11 2:17 ` Juanma Barranquero
2008-09-11 2:21 ` Juanma Barranquero
2008-09-12 6:32 ` Kenichi Handa
2008-09-12 8:56 ` Juanma Barranquero
2008-09-03 16:21 ` bug#874: " Juanma Barranquero
2008-09-04 15:25 ` Juanma Barranquero [this message]
2008-09-12 9:05 ` bug#874: marked as done (Args out of range with new auto-composition implementation) Emacs bug Tracking System
2008-09-11 14:46 ` Args out of range with new auto-composition implementation Ted Zlatanov
2008-09-24 6:07 ` Kenichi Handa
2008-10-08 16:58 ` Ted Zlatanov
2008-10-10 1:49 ` Kenichi Handa
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=f7ccd24b0809040825h29f4a1etd2c70a4098fb865@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=874@emacsbugs.donarmstrong.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.