taskLiberty Eiffel - Tasks: task #13457, static checks for memory allocation

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #13457: static checks for memory allocation

Submitter:  Raphael Mack <ramack>
Submitted:  Sat 24 Jan 2015 08:06:16 PM UTC
Votes:  1  
 
Should Start On:  Fri 23 Jan 2015 11:00:00 PM UTC Should be Finished on:  Mon 23 Jan 2017 11:00:00 PM UTC
Category:  SmartEiffel Priority:  3 - Low
Status:  None Percent Complete:  0%
Assigned to:  None Open/Closed:  Open
Fixed Release:  None Planned Release:  None
Effort:  0.00

Sun 13 Feb 2022 07:32:02 AM UTC, comment #3: 

I think it would be great to have, but on a Raspberry Pi we wouldn't need it. So for me it would be cool as a long term idea but should not care too much about it as long as our test suite so so dark red as currently.

Raphael Mack <ramack>
Project Administrator
Wed 09 Feb 2022 07:56:38 AM UTC, comment #2: 

Is this topic still on our radar?  I'd really like to be able to ensure that all allocations are done at application start-up and then no further allocations during run-time.  Especially in the realm of ARM proliferation (Raspberry Pi, Arduino, etc.)  it would be great to be able to work with static memory allocation only...

Zwakenberg <hzwakenberg>
Project Member
Sat 07 Feb 2015 01:44:07 PM UTC, comment #1: 

"For example in embedded devices with realtime constraints and functional safety classification I don't see how a system with garbage collector may ever be used, while contracts and the rigor of Eiffel would be great!"

I can't agree more!

Zwakenberg <hzwakenberg>
Project Member
Sat 24 Jan 2015 08:06:16 PM UTC, original submission:  

See task #13456 we should add a static check to warn at compile time if a dispose feature allocates memory.

I'd even like to go further and suggest a generic mechanism for memory allocation observation. I think of systems without GC and compiler support to ensure, that after initialization no more memory allocation will be done.

For example in embedded devices with realtime constraints and functional safety classification I don't see how a system with garbage collector may ever be used, while contracts and the rigor of Eiffel would be great!

Raphael Mack <ramack>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by hzwakenberg (Voted in favor of this item)
  • -email is unavailable- added by hzwakenberg (Posted a comment)
  • -email is unavailable- added by ramack (Submitted the item)
  •  

    There is 1 vote so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

     

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2015-02-07 hzwakenberg Carbon-Copy- Added hzwakenberg

    Back to the top


    Powered by Savane 3.9