%% Ted Stern <[EMAIL PROTECTED]> writes: ts> Nevertheless, I wonder if there might be an alloca-type memory ts> leak going on here.
Nope. Sorry, Ted, but you're alone in this :-). All the other environments, including Windows IIRC, have a real alloca() implementation. This allocates memory on the stack, and so alloca(0) is completely unnecessary: as soon as the function returns all info on the stack is freed. On these systems, in fact, alloca(0) is a no-op. The OP's issue is clearly an instance of bug #1517: https://savannah.gnu.org/bugs/index.php?func=detailitem&item_id=1517 -- ------------------------------------------------------------------------------- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org "Please remain calm...I may be mad, but I am a professional." --Mad Scientist _______________________________________________ Help-make mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-make
