On Wednesday 28 October 2009 03:47:03 Mike Frysinger wrote: > while the memory leakage needs to be addressed, the answer isnt with > alloca. the spec states that it must be via malloc(), but even ignoring > that, it also states that the caller must call free() on the returned > pointer. obviously alloca-ed memory is not valid outside of the return of > realpath() (which makes me wonder how your code even worked in the first > place), nor can you call free() on it.
nm, i'm retarded. i'd forgotten about the strdup() at the end. -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
