Home/ Questions/Q 7706985
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T00:14:48+00:00

(or so I think)… I’m using boost::xpressive as my regular expression engine to parse

  • 0

(or so I think)…

I’m using boost::xpressive as my regular expression engine to parse something and I get a segfault. I suspect that recursivity and my bad regular expression are to blame, because gdb shows more than 300 stack frames. So, here is my (case-sensitive) regular expression, in perl/python notation:

begin([^e]+)e((?:[^b]|b(?!egin))+)

which I expect to match 

beginHEADER HEREeFOLLOWED BY SOME LONG LONG TEXT THAT GOES UNTIL NEXTbegin

with the first uppercase text (HEADER HERE) in the first group, and the second uppercase text in the second group. I always get the segfault if the text that should match group 2 is very long.

Why shouldn’t this work?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can simplify your regular expression a lot by simply using non-greedy matching:

    begin(.+?)e(.+?)begin

    Try that and see if it works better.

    It’s likely that your original regex was causing a stack overflow due to a recursive implementation of the |-or grouping in your regex, which was potentially branching with every single character in your second group.

    A simple non-greedy .+? on the other hand doesn’t need to branch for every single character.

    • 0