On 16 December 2012 02:18, Paul Eggert <egg...@cs.ucla.edu> wrote: > On 12/15/2012 03:08 PM, Jeffrey Walton wrote: >> >> Is the program designed to remove old core >> files as part of the autoconf process? > > > No, new cores. 'configure' regularly generates > programs that dump core, as part of its ordinary > working procedure.
Does it make sure core is new one it has created. Granted that if one wants to play with core generated by the program being developet, (s)he shouldn't be rebuilding program before those investigations, but potentially core file is valuable. Is the performance issue in the checking of nature of "core" *every time* configure has potentially created one to be removed? Could it just check existing situation in the beginning (is there something named 'core' already) and to store it to variable for later parts to use? - ML _______________________________________________ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
