Re: Vim: Caught deadly signal ABRT

[Ottavio Caruso <ottavio2006-usenet2012%yahoo.com@localhost>]

On Thu, 11 Jul 2019 at 14:11, Martin Husemann <martin%duskware.de@localhost> wrote:
>
> On Thu, Jul 11, 2019 at 01:23:26PM +0100, Ottavio Caruso wrote:
> > I was on freenode#pkgsrc right now. Leo Taccari just suggested to rebuild with:
> >
> > env CFLAGS=-g INSTALL_UNSTRIPPED=yes bmake replace
> >
> > and indeed it's now working fine.
>
> Maybe try with: env CFLAGS="-g -O2" INSTALL_UNSTRIPPED=yes bmake replace
>
> .. and see if it crashes again. But then you should be able to look at
> the core files with gdb and get proper debug output.
>
> > Is this something that should be reported upstream?
>
> Yes, but with more complete analyzis (or they likely can't do much about it).
>
> Martin

As pointed out by  Bram Moolenaar on vim_use:

"you run into the false-positive fortify check."
 "Although the build log mentiones -D_FORTIFY_SOURCE=1 it behaves like
a  higher fortify level was used."

I'm not sure if this is related, but I see this in .work.log:

<.> /home/oc/pkgsrc/work/editors/vim/work/.gcc/bin/gcc -m64 --version
-std=gnu99 -D_FORTIFY_SOURCE=2 -fstack-protector
-I/home/oc/pkgsrc/work/editors/vim/work/.buildlink/include
[*] cc -v
<.> /home/oc/pkgsrc/work/editors/vim/work/.gcc/bin/gcc -m64 -v
-std=gnu99 -D_FORTIFY_SOURCE=2 -fstack-protector
-I/home/oc/pkgsrc/work/editors/vim/work/.buildlink/include
[*] cc -V
<.> /home/oc/pkgsrc/work/editors/vim/work/.gcc/bin/gcc -m64 -V
-std=gnu99 -D_FORTIFY_SOURCE=2 -fstack-protector
-I/home/oc/pkgsrc/work/editors/vim/work/.buildlink/include
[*] cc -qversion
<.> /home/oc/pkgsrc/work/editors/vim/work/.gcc/bin/gcc -m64 -qversion
-std=gnu99 -D_FORTIFY_SOURCE=2 -fstack-protector
-I/home/oc/pkgsrc/work/editors/vim

"D_FORTIFY_SOURCE=2" is found 571 times in this log.



-- 
Ottavio Caruso