Eric Blake <ebb9 <at> byu.net> writes: > > Karl's observation on bug-m4 that we had a bogus warning pointed out something > even more severe - we were reading uninitialized memory from the stack. > Depending on your hardware, you can get allocation failures, core dumps, and > possibly even arbitrary code execution.
I still need to work on this. We have a memory leak (and have done, since m4 0.75 when regexp was introduced), because re_search allocates memory in re_registers on success if we haven't done it ourselves. -- Eric Blake _______________________________________________ M4-patches mailing list [email protected] http://lists.gnu.org/mailman/listinfo/m4-patches
