This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
about libc function interfaces and ld --wrap
- From: "sean yang" <seanatpurdue at hotmail dot com>
- To: binutils at sourceware dot org
- Cc: drepper at redhat dot com, nickc at redhat dot com
- Date: Fri, 03 Mar 2006 22:24:48 +0000
- Subject: about libc function interfaces and ld --wrap
- Bcc:
Several question to ask about libc and linker:
(1) I would ask general glibc design question: whether an exported function
in glibc can be called by another function internally?
For example (--which is a faked example),
malloc is an exported function;
foo(this is a faked name example) is another exported function;
** is it possible that foo( ) calls malloc( ) internally?
(2) If the answer to above question is yes, then the following that question
is: if I have printf wrapped by my own layer (by "ld --wrap printf"), will
_wrap_malloc() change the internal call's behavior?
void *
__wrap_ malloc(int c)
{
printf ("Coming here\n", c);
return __real_malloc (c);
}
(3) If there a convenient way to wrap multi function, e.g., malloc, printf,
getc...., with same "added functionality" (say just print "coming here"). I
mean an better way than create each wrapper seperately?
_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement