Re: NSRegularExpression segfault
Re: NSRegularExpression segfault
- Subject: Re: NSRegularExpression segfault
- From: ecir hana <email@hidden>
- Date: Mon, 15 Dec 2014 18:59:23 +0100
On Mon, Dec 15, 2014 at 6:50 PM, Stephen J. Butler <email@hidden
> wrote:
>
> It seems to be related to the number of capture groups you have. For
> example, this also succeeds for me:
>
>
> ((?:1+)|(?:2+)|(?:3+)|(?:4+)|(?:5+)|(?:6+)|(?:7+)|(?:8+)|(?:9+)|(?:0+)|(?:a+))
>
> Do you really need the 11 capture groups?
>
Thanks for giving it a try!
It's not precisely 11, but yes, I need to have many. I also discovered it
is related to the number of capture groups and their "complexity". One
single group works for much longer inputs but I guess you already know that.
To put it differently, even if I could reduce the number of groups a bit, I
think I will still hit that segfault for some non-trivial inputs. For
example, when I only use 6 groups it still segfaults at around 80 000
characters.
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden