Hi lee On 2015-12-29, lee wrote:
> When you perform a strcpy() and overflow the destination buffer, you are > supposed to experience a segmentation fault. It shouldn't matter > whether you run a hardened profile or not for detecting these. Ok. Thanks for the explanation. > I imagine it was discovered that a segmentation fault did occur, and > that it inevitably would occur --- since gcc tells you that one will > occur when using __builtin___strcpy_chk() --- and the application was > terminated. Otherwise, the test would have been unsuccessful. Ok. > Whether this is a bug or not depends on what you're supposed to expect, > which I don't know. If someone would run the test suite on a > non-hardened profile and got the same warning from gcc, but vim wouldn't > be terminated when the segmentation fault occurs, then I'd be worried. Ok. Well, I don't know either what to expect. I haven't got enough knowledge to analyse this. I posted it here because I was told so ;-) -- Greetings Elias
