Subject: Re: bug#22310: Segmentation fault in regular expression matcher

From: Eli Zaretskii <[email-masked]>
Date: Tue, 05 Jan 2016 18:08:38 +0200

> From: Ben Gamari <[email-masked]>
> Date: Tue, 05 Jan 2016 13:15:54 +0100
> 
> While editing a Markdown document with markdown-mode and revision
> 138480a97bfc1104143b5fc10dfc962b95b78ae8 I encountered this segmentation
> fault,
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000538ae8 in re_match_2_internal (bufp=bufp@entry=0xb8f398 <searchbufs+2552>,
>     string1=string1@entry=0x53b1200 "---\ntitle: Understanding GHC Core\ndate: 2015-11-29\ntags: ghc,core,work-in-progress\ndescription: Everything you really need to know to understand GHC's Core\n---\n**This document is a work-in-progress.**"..., size1=size1@entry=1782,
>     string2=string2@entry=0x53b20d1 "\n\n`cast`\n\n`Sym`\n\n`Sub`\n\n`<ty>_R` is a type parameter with representational role. Roughly speaking this\nmeans that given a type constructor `T` and types `A` and `B`, `T <A>_R` and `T\n<B>_R` are repres"..., size2=size2@entry=9296, pos=pos@entry=4281,
>     regs=0xb8e970 <search_regs>, stop=11078) at regex.c:5556
> 5556		  PUSH_FAILURE_REG (*p);

Please update to the latest master and see if the problem goes away.
It's possible that this was already solved by one of the commits since
you last updated.

Thanks.