[RTEMS Project] #2528: Update https://devel.rtems.org/wiki/TBR/Delete/NewlibMemoryAllocation

[RTEMS trac]

#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 think I've underestimated the work involved in producing a useful
 breakdown in a maintainable and error-free way, here.

 Whilst I could just produce a list of files, line numbers and functions
 directly calling e.g., ''malloc()'', I don't think that's very useful...
 What I'd like to know, as an application developer, is what functions I
 might call from my application that might result in memory allocation
 attempts. A simple grep's going to turn up lots of implementation detail
 (e.g., file-static functions that call malloc(), whereas I'd want instead
 the functions that are exposed to RTEMS applications that might call it).

 Add in function pointers (e.g., ''ucs_2_init()'' in ''iconv/ces/ucs-2.c''
 is pointed to by ''_iconv_to_ucs_ces_handlers_ucs_2.init'', the latter
 struct then gets indexed by string in ''iconv_to_ucs_ces_t
 _iconv_to_ucs_ces''), and a bunch 'o ''#defines'' and... my brain hurts.

 Can anyone suggest tools which might help here? Otherwise we should
 perhaps just delete the article...

--
Ticket URL: <http://devel.rtems.org/ticket/2528#comment:11>
RTEMS Project <http://www.rtems.org/>
RTEMS Project