Steps to reproduce:


1) find or create an attribute which has an ORDERING matching rule
(and not via inheritance - that's another bug)

ldapmodify -x -h localhost -p 1389 -D "cn=directory manager" -w ggg -v <<
EOF
dn: cn=schema
changetype: modify
add: attributetypes
attributeTypes: (1.3.6.1.4.1.34217.1.1.1.2.6 NAME
'nzCoSkyReceiveMarketingNewsLetter' DESC 'Whether the user opts to receive SKY
TV news letters' EQUALITY booleanMatch ORDERING booleanMatch SYNTAX
1.3.6.1.4.1.1466.115.121.1.7 SINGLE-VALUE)

add attributeTypes:
(1.3.6.1.4.1.34217.1.1.1.2.6 NAME 'nzCoSkyReceiveMarketingNewsLetter' DESC
'Whether the user opts to receive SKY TV news letters' EQUALITY booleanMatch
ORDERING booleanMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 SINGLE-VALUE)
modifying entry "cn=schema"
modify complete

2) add or change the index for the attribute to have an nsMatchingRule
with one of the l10n matching rules defined by the collation plugin
e.g. 2.16.840.1.113730.3.3.2.11.1 for en or en-US
[root@rheltest slapd-rheltest]# ldapmodify -a -D "cn=directory manager" -w
ggg -p 1389 -h localhost << EOF
>  dn: cn=nzCoSkyReceiveMarketingNewsletter,cn=index,cn=userRoot,cn=ldbm
>  database,cn=plugins,cn=config
>  changetype: add
>  objectClass: top
>  objectClass: nsIndex
>  cn:nzCoSkyReceiveMarketingNewsletter
>  nsSystemIndex:false
>  nsIndexType:eq
>  nsMatchingRule: 2.16.840.1.113730.3.3.2.6.1
>  nsMatchingRule: 2.16.840.1.113730.3.3.2.11.1
>  EOF
ldapmodify: invalid format (line 2) entry:
"cn=nzCoSkyReceiveMarketingNewsletter,cn=index,cn=userRoot,cn=ldbm"
Segmentation fault (core dumped) 

Note: The dn: .. line must be all one line.  It looks like the line ends at cn=ldbm and a new line begins at database,. 
But still it should not be a Segmentation fault (core dumped).