Re: capture engine use of workspace_allocate

2014-07-23 Thread Chris Johns
On 22/07/2014 1:47 am, Joel Sherrill wrote: On July 21, 2014 10:44:15 AM CDT, Gedare Bloom wrote: Either account for it in workspace sizing or use malloc. On principle, I guess any dynamic allocated memory that isn't mandatory to get RTEMS to work should come from malloc. With one malloc a

Re: capture engine use of workspace_allocate

2014-07-23 Thread Chris Johns
On 22/07/2014 1:47 am, Joel Sherrill wrote: On July 21, 2014 10:44:15 AM CDT, Gedare Bloom wrote: Either account for it in workspace sizing or use malloc. On principle, I guess any dynamic allocated memory that isn't mandatory to get RTEMS to work should come from malloc. With one malloc a

Re: capture engine use of workspace_allocate

2014-07-21 Thread Joel Sherrill
On July 21, 2014 10:44:15 AM CDT, Gedare Bloom wrote: >Either account for it in workspace sizing or use malloc. > >On principle, I guess any dynamic allocated memory that isn't mandatory >to get RTEMS to work should come from malloc. With one malloc and two workspace allocates, I assumed we sho

Re: capture engine use of workspace_allocate

2014-07-21 Thread Gedare Bloom
Either account for it in workspace sizing or use malloc. On principle, I guess any dynamic allocated memory that isn't mandatory to get RTEMS to work should come from malloc. -Gedare On Mon, Jul 21, 2014 at 10:41 AM, Jennifer Averett < jennifer.aver...@oarcorp.com> wrote: > The capture engine c