CVSROOT: /sources/m4 Module name: m4 Branch: branch-1_4 Changes by: Eric Blake <ericb> 06/10/26 04:45:31
Index: doc/m4.texinfo =================================================================== RCS file: /sources/m4/m4/doc/m4.texinfo,v retrieving revision 1.1.1.1.2.93 retrieving revision 1.1.1.1.2.94 diff -u -b -r1.1.1.1.2.93 -r1.1.1.1.2.94 --- doc/m4.texinfo 25 Oct 2006 20:54:39 -0000 1.1.1.1.2.93 +++ doc/m4.texinfo 26 Oct 2006 04:45:31 -0000 1.1.1.1.2.94 @@ -3561,6 +3561,20 @@ f divert(`-1')undivert @end example + [EMAIL PROTECTED] We also need to test allocation overflow. On 32-bit [EMAIL PROTECTED] platforms, this should fail outright. But on 64-bit platforms [EMAIL PROTECTED] with enough memory, the allocation might succeed (hopefully [EMAIL PROTECTED] testers don't mind the memory thrashing), so fake the same [EMAIL PROTECTED] output for test success. + [EMAIL PROTECTED] +divert(eval(`1<<28')) +divert(`2') +errprint(__program__`: memory exhausted +')m4exit(`1') [EMAIL PROTECTED]: memory exhausted [EMAIL PROTECTED] example @end ignore @c FIXME: need some explanation here why this is a useful feature, not
