unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: 23869@debbugs.gnu.org
Subject: bug#23869: 25.0.95; replace-match can crash emacs
Date: Wed, 29 Jun 2016 18:37:02 +0300	[thread overview]
Message-ID: <837fd8vwf5.fsf@gnu.org> (raw)
In-Reply-To: <m137nwhyfj.fsf@gmail.com> (message from Leo Liu on Wed, 29 Jun 2016 22:17:20 +0800)

> From: Leo Liu <sdl.web@gmail.com>
> Date: Wed, 29 Jun 2016 22:17:20 +0800
> 
> Under some circumstances replace-match can crash emacs. It takes a lot
> to reproduce the crash and I haven't been able to find a minimal
> example. But I wonder if the backtrace that I captured in LLDB can give
> any clue to the clause? I can't reproduce the same crash in emacs24.

Do you still have this crashed session in a debugger?  Because some of
the values involved in this crash are not clear or not shown.

>     frame #1: 0x000000010028356a emacs`set_point_both(charpos=-1, bytepos=-1) + 234 at intervals.c:1921
>     frame #2: 0x0000000100283476 emacs`set_point(charpos=-1) + 54 at intervals.c:1816
>     frame #3: 0x0000000100284597 emacs`move_if_not_intangible(position=-1) + 855 at intervals.c:2157

The immediate reason is obviously the POSITION = -1 above, but the
question is: how did replace-match allow that to happen?  It's a large
function, so it's hard to tell how this could happen without seeing
some of the variables there.

Do you perhaps remember or know what text was replaced by what when
this happened?





  reply	other threads:[~2016-06-29 15:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 14:17 bug#23869: 25.0.95; replace-match can crash emacs Leo Liu
2016-06-29 15:37 ` Eli Zaretskii [this message]
2016-06-29 16:00   ` Leo Liu
2016-06-29 16:07     ` Eli Zaretskii
2016-06-30  3:27       ` Leo Liu
2016-06-30 15:04         ` Eli Zaretskii
2016-07-03 18:53           ` Leo Liu
2016-07-03 19:32             ` Eli Zaretskii
2016-07-03 20:08           ` Stefan Monnier
2016-07-03 20:33             ` Eli Zaretskii
2016-07-03 21:06               ` Stefan Monnier
2016-07-04 15:36                 ` Eli Zaretskii
2016-07-06 14:32                   ` Robert Pluim

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=837fd8vwf5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23869@debbugs.gnu.org \
    --cc=sdl.web@gmail.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 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).