JehanneOS/newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Entry 'Can I use my own malloc?': Add warning about _malloc_r from newlib.

Browse Source
This commit is contained in:
David Starks-Browning 2000-07-25 19:50:31 +00:00
parent 7e0482eecd
commit 717a3d7b37
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
winsup/doc/how.texinfo
View File

@ -1305,9 +1305,6 @@ Include stdlib.h instead of malloc.h.
@subsection Can I use my own malloc?
@strong{(Please note: This section has not yet been updated for the latest
net release.)}
If you define a function called @code{malloc} in your own code, and link
with the DLL, the DLL @emph{will} call your @code{malloc}. Needless to
say, you will run into serious problems if your malloc is buggy.
@ -1318,6 +1315,14 @@ This process uses @code{malloc} @emph{before} your main line is started.
If you have written your own @code{malloc} to need some initialization
to occur after @code{main} is called, then this will surely break.
Moreover, there is an outstanding issue with @code{_malloc_r} in
@code{newlib}. This re-entrant version of @code{malloc} will be called
directly from within @code{newlib}, by-passing your custom version, and
is probably incompatible with it. But it may not be possible to replace
@code{_malloc_r} too, because @code{cygwin1.dll} does not export it and
Cygwin does not expect your program to replace it. This is really a
newlib issue, but we are open to suggestions on how to deal with it.
@subsection Can I mix objects compiled with msvc++ and gcc?
Yes, but only if you are combining C object files. MSVC C++ uses a