Re: [gentoo-user] Maybe bug? (glibc related?)

Hi lee On 2015-12-30, lee wrote: > Elias Diem writes: > > >> 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 terminate

Re: [gentoo-user] Maybe bug? (glibc related?)

Elias Diem writes: >> 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

Re: [gentoo-user] Maybe bug? (glibc related?)

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 dis

Re: [gentoo-user] Maybe bug? (glibc related?)

Elias Diem writes: > Hi lee > > On 2015-12-29, lee wrote: > >> Elias Diem writes: >> >> > Hi >> > >> > I just got the following while running Vim's testsuite. >> > >> > >> > *** buffer overflow detected ***: vim terminated; report to >> > >> > Makefile:151: recipe fo

Re: [gentoo-user] Maybe bug? (glibc related?)

Hi lee On 2015-12-29, lee wrote: > Elias Diem writes: > > > Hi > > > > I just got the following while running Vim's testsuite. > > > > > > *** buffer overflow detected ***: vim terminated; report to > > > > Makefile:151: recipe for target 'af.ck' failed > > make[2]:

Re: [gentoo-user] Maybe bug? (glibc related?)

Elias Diem writes: > Hi > > I just got the following while running Vim's testsuite. > > > *** buffer overflow detected ***: vim terminated; report to > > Makefile:151: recipe for target 'af.ck' failed > make[2]: *** [af.ck] Killed > > > The compiler gave me the follow