#2528: Update https://devel.rtems.org/wiki/TBR/Delete/NewlibMemoryAllocation --------------------------+--------------------------- Reporter: nick.withers | Owner: nick.withers Type: defect | Status: accepted Priority: normal | Milestone: 4.11.1 Component: Newlib | Version: 4.11 Severity: normal | Resolution: Keywords: | --------------------------+---------------------------
Comment (by nick.withers): I don't think cflow (or cscope) can handle e.g., calls through function pointers. > But this also might be a good discussion to move to newlib's mailing list. What we really want is to know which public API calls can result in memory allocation Agreed, and well put. Ideally they'd maintain that information and insist it were updated when commits change the situation -- Ticket URL: <http://devel.rtems.org/ticket/2528#comment:13> RTEMS Project <http://www.rtems.org/> RTEMS Project _______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
