GNU bug report logs - #10913
24.0.94; Crash in redisplay code

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jan Djärv <jan.h.d <at> swipnet.se>
Cc: azure <at> iki.fi, 10913 <at> debbugs.gnu.org
Subject: bug#10913: 24.0.94; Crash in redisplay code
Date: Thu, 01 Mar 2012 06:04:28 +0200

> From: Jan Djärv <jan.h.d <at> swipnet.se>
> Date: Wed, 29 Feb 2012 22:23:48 +0100
> Cc: Hannu Koivisto <azure <at> iki.fi>,
>  10913 <at> debbugs.gnu.org
> 
> > 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.

True.  Exactly the reason why I wrote that I don't believe this
backtrace.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.