Ticket #38 (closed Bug: fixed)
Buffer analysis
| Reported by: | R. Couillet | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 3.1 |
| Component: | binaries | Version: | |
| Keywords: | Cc: |
Description
- when consuming outside of buffer capacity, Cheddar crashes if
you do a buffer analysis from simulation.
- sometimes, when setting a producer/consumer design, the first
instance of the comsumer task doesn't consume (which is implicitely great
because buffer is not filled enough of data), then the next instance
consumes all data (which is great again because this time buffer is full
enough) but the next one also consumes from the buffer while this one is
not filled enough... so I guess either the first or the third occurence
of this task doesn't behave well.
- something that's not exactly a bug: i didn't find out any way to
read from or write to a buffer during more than 1 unit of time... is it a
default behaviour of Cheddar?, can we handle that differently?
Attachments
Change History
comment:1 Changed 9 years ago by jlegrand
In the last svn revision (1883), cheddar still crash when one does a buffer analysis from simulation.
For the next 2 points :
- In cheddar, a consumer consums (or tries to) data each time it is activate.
- In cheddar, if one want to access a memory resource for a period of time, the "resource" paradigm shall be used.
Note : the buffer.xml has been updated to V3
