[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Vim: Caught deadly signal ABRT
On Thu, 11 Jul 2019 at 11:19, Benny Siegert <bsiegert%gmail.com@localhost> wrote:
> I have seen similar aborts with vim from pkgsrc on ChromeOS. I assume
> it is a real bug (buffer overrun or something) that is found by our
> various hardening systems.
[added morr to cc]
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.
Is this something that should be reported upstream?
> On Thu, Jul 11, 2019 at 12:38 AM Ottavio Caruso
> <ottavio2006-usenet2012%yahoo.com@localhost> wrote:
> > Hi all,
> > pkgsrc branch: both -current and -2019Q2
> > $ uname -a
> > Linux e130 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21)
> > x86_64 GNU/Linux
> > Successfully built, made package and installed editors/vim, but it
> > crashes on start:
> > $vim
> > Vim: Caught deadly signal ABRT
> > Vim: Finished.
> > Output of `vim --version` here:
> > http://paste.debian.net/hidden/d3766598/
> > Build log here:
> > http://paste.debian.net/hidden/6ba63958/
> > I see a lot of references to:
> > <command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
> > <command-line>:0:0: note: this is the location of the previous definition
> > Is that a possible clue?
> > Any input will be appreciated.
> > --
> > Ottavio Caruso
Main Index |
Thread Index |