PR# 17640 > 268 TUPLE fields leads to runtime segfault

Problem Report Summary
Submitter: soapy2357
Category: Runtime
Priority: Medium
Date: 2011/06/12
Class: Bug
Severity: Serious
Number: 17640
Confidential: No
Status: Analyzed
Environment: Linux, 32bit
Synopsis: > 268 TUPLE fields leads to runtime segfault

If more than 268 tuple fields are declared, the program segfaults at runtime trying to create the tuple.
If there's indeed a limit on the number of fields, then an Eiffel compilation error should be shown, not a runtime segfault. But of course it would be best if an arbitrary number of fiels would be allowed.
To Reproduce
Run the attached testclass. It declares 269 fields and therefore segfaults at runtime.
Problem Report Interactions
From:manus_eiffel    Date:2011/06/13    Status: Analyzed    Download   
This is a known limitation but not just for TUPLE. It affects all generic classes. Unfortunately this is not an easy thing to detect at compile time. This is more a runtime limitation since at runtime you can create types that did not even exist at compile time.

From:soapy2357    Date:2011/06/12    Download   
Attachments for problem report #17640

Attachment: testbed.e     Size:7946