My setup is as mentioned in <[EMAIL PROTECTED]>, hence it is not a pure HLFS setup.
Test program is the one from the book:
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
static void raw(char *, size_t);
static void
raw(char *b, size_t len) {
b[len] = '\0';
}
int
main(int argc, char *argv[])
{
char b[10];
size_t len = atoi(argv[1]);
(void)strncpy(b, "0000000000", sizeof(b));
raw(b, len);
(void)printf("%s\n", b);
return 0;
}
Compiled with
gcc -U_FORTIFY_SOURCE overflow.c -o overflow
and invoked this way:
./overflow 10 > out 2>&1
The file `out' is then examined. A success is if it contains the string
'Aborted' and not the string 'segmentation fault' (case-insensitive). I did
several 10.000 runs, and in some cases (no more then 0.5%), the outcome is
*not* a success. But instead, the file `out' contains the output of the
program, i.e., 0000000000.
Is this the expected behavior? Could it become a problem?
What could I try to track this down further?
pgpAtrmJjT3sR.pgp
Description: PGP signature
-- http://linuxfromscratch.org/mailman/listinfo/hlfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
