From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Hannu Koivisto <azure@iki.fi>, 10913@debbugs.gnu.org
Subject: bug#10913: 24.0.94; Crash in redisplay code
Date: Wed, 29 Feb 2012 22:23:48 +0100 [thread overview]
Message-ID: <25ECBDF6-A273-4D79-8DC6-4B34002790E9@swipnet.se> (raw)
In-Reply-To: <83fwdtcwuo.fsf@gnu.org>
29 feb 2012 kl. 19:34 skrev Eli Zaretskii:
>> From: Hannu Koivisto <azure@iki.fi>
>> Date: Wed, 29 Feb 2012 18:12:35 +0200
>>
>> Random crash. I don't know how to reproduce this. Backtrace included
>> below. Some string variable contents have been changed from what
>> they really were.
>
> This is an optimized build, right? Otherwise, some variables shown
> here make no sense at all. E.g., this:
>
>> #3 0x010873f3 in fast_looking_at (regexp=6, pos=676026, pos_byte=96427,
>> limit=89596416, limit_byte=285891, string=1) at search.c:588
>
> `regexp' is a Lisp string, so it cannot have this value. And `pos'
> and `limit' are likewise garbled.
>
> Anyway, if I'm to believe this backtrace (which I don't, since the
> build is evidently optimized), the crash happened here:
>
> switch (SWITCH_ENUM_CAST ((re_opcode_t) *pat++))
> {
> case on_failure_keep_string_jump:
> assert (str == NULL);
> goto continue_failure_jump;
>
> case on_failure_jump_nastyloop:
> assert ((re_opcode_t)pat[-2] == no_op);
> PUSH_FAILURE_POINT (pat - 2, str);
> /* Fallthrough */
> ...
> default:
> abort (); <<<<<<<<<<<<<<<<<<<<<
> }
>
> which means what? that compile_pattern produced an invalid result?
> I'd be surprised.
Remember that optimization may join aborts together, so they look like they happened there, but it can be just about any abort in that file.
Jan D.
next prev parent reply other threads:[~2012-02-29 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 16:12 bug#10913: 24.0.94; Crash in redisplay code Hannu Koivisto
2012-02-29 18:34 ` Eli Zaretskii
2012-02-29 21:23 ` Jan Djärv [this message]
2012-03-01 4:04 ` Eli Zaretskii
2012-03-01 7:53 ` Hannu Koivisto
2013-02-17 3:22 ` Glenn Morris
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=25ECBDF6-A273-4D79-8DC6-4B34002790E9@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=10913@debbugs.gnu.org \
--cc=azure@iki.fi \
--cc=eliz@gnu.org \
/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.