Add a function call stackprotector tests.

Including a function call in the test programs for the gcc stack
protector flag tests exercises more of the compiler and makes it more
likely it'll detect problems.

1 files changed, 10 insertions, 4 deletions

diff --git a/configure.ac b/configure.ac
index 3e93c0276..8bc96bb45 100644
--- a/configure.ac
+++ b/configure.ac
@@ -213,20 +213,26 @@ if test "$GCC" = "yes" || test "$GCC" = "egcs"; then
                 CFLAGS="$CFLAGS $t -Werror"
                 LDFLAGS="$LDFLAGS $t -Werror"
                 AC_LINK_IFELSE(
-                        [AC_LANG_PROGRAM([[ #include <stdio.h> ]],
+                        [AC_LANG_PROGRAM([[
+        #include <stdio.h>
+        int func (int t) {char b[100]; snprintf(b,sizeof b,"%d",t); return t;}
+                         ]],
                         [[
         char x[256];
-        snprintf(x, sizeof(x), "XXX");
+        snprintf(x, sizeof(x), "XXX%d", func(1));
                          ]])],
                     [ AC_MSG_RESULT([yes])
                       CFLAGS="$saved_CFLAGS $t"
                       LDFLAGS="$saved_LDFLAGS $t"
                       AC_MSG_CHECKING([if $t works])
                       AC_RUN_IFELSE(
-                        [AC_LANG_PROGRAM([[ #include <stdio.h> ]],
+                        [AC_LANG_PROGRAM([[
+        #include <stdio.h>
+        int func (int t) {char b[100]; snprintf(b,sizeof b,"%d",t); return t;}
+                        ]],
                         [[
         char x[256];
-        snprintf(x, sizeof(x), "XXX");
+        snprintf(x, sizeof(x), "XXX%d", func(1));
                         ]])],
                         [ AC_MSG_RESULT([yes])
                           break ],