capture engine use of workspace_allocate

[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.Averett at oarcorp.com> wrote:

> The capture engine currently uses a mixture of malloc and
>
> rtems_workspace_allocate.  We don’t think the workspace
>
> accounts for this, and would like to propose changing it
>
> so that malloc is used for all memory allocation.  Does anyone
>
> see any reason this shouldn’t be done?
>
>
>
> --jennifer
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20140721/e3aaec65/attachment-0002.html>