asn1 compilation with parameter and extension fails

[sebastiw]

Describe the bug
Compilation of an ASN.1 module fails if it contains a parameterized type with an inner SEQUENCE containing an extension marker. It might be related to #4514

To Reproduce

CAP-datatypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-datatypes(52) version8(7)}

DEFINITIONS ::= BEGIN

    Digits {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE(
	bound.&minDigitsLength .. bound.&maxDigitsLength))

    BasicGapCriteria {PARAMETERS-BOUND : bound} ::= CHOICE {
       calledAddressAndService [29] SEQUENCE {
           calledAddressValue [0] Digits {bound},
           ...
       }
    }

END

erlc asn1/CAP-datatypes.asn1
Internal error: error:function_clause
[{asn1ct_gen,do_gen_record_1,
             [[{'EXTENSIONMARK',11,undefined}]],
             [{file,"asn1ct_gen.erl"},{line,1277}]},
 {asn1ct_gen,do_gen_record_1,1,[{file,"asn1ct_gen.erl"},{line,1290}]},
 {asn1ct_gen,do_gen_record,3,[{file,"asn1ct_gen.erl"},{line,1271}]},
 {asn1ct_gen,gen_record,5,[{file,"asn1ct_gen.erl"},{line,1234}]},
 {asn1ct_gen,gen_record,5,[{file,"asn1ct_gen.erl"},{line,1191}]},
 {asn1ct_gen,pgen_hrltypes,4,[{file,"asn1ct_gen.erl"},{line,1166}]},
 {asn1ct_gen,pgen_hrl,2,[{file,"asn1ct_gen.erl"},{line,1126}]},
 {asn1ct_gen,pgen,3,[{file,"asn1ct_gen.erl"},{line,69}]}]

Expected behavior
If the inner SEQUENCE is broken out into it's own type it compiles. I'm expecting the same behaviour.

CAP-datatypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-datatypes(52) version8(7)}

DEFINITIONS ::= BEGIN

    Digits {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE(
	bound.&minDigitsLength .. bound.&maxDigitsLength))

    BasicGapCriteria {PARAMETERS-BOUND : bound} ::= CHOICE {
       calledAddressAndService [29] CalledAddressAndService {bound}
    }

    CalledAddressAndService {PARAMETER-BOUND : bound} ::= SEQUENCE {
           calledAddressValue [0] Digits {bound},
           ...
    }
END

Affected versions
Erlang/OTP 24.0.1 [erts-12.0.1] with asn1-5.0.16

Additional context
For reference the spec ETSI TS 129 078 V15.0.0 have this behaviour (CAMEL Application Part)

[KennethL]

I can confirm that it is the same type of problem as in #4514 and the solution there does not solve all cases. This is nothing new, it is the same behavior in OTP 23 and I suspect all previous OTP versions.

[KennethL]

Solution is now pushed to maint and master. Will be part of next official patch on the 23 track and will be part of OTP 24.1 when it is released in September