[vim/vim] Segmentation fault when trying to write scheme code (Issue #9062)

133 views
Skip to first unread message

TruncatedDinosour

unread,
Oct 28, 2021, 7:43:11 PM10/28/21
to vim/vim, Subscribed

Steps to reproduce

  1. Open vim
  2. Open a terminal (:term)
  3. Unfocus the terminal window vim is in
  4. Open an image on telegram (as a file)
  5. Close the image
  6. Breaks

Expected behaviour

For it to stay open

Operating system

Linux ari-gentoo 5.14.15-gentoo #2 SMP Thu Oct 28 08:43:20 EEST 2021 x86_64 Intel(R) Core(TM) i3-8130U CPU @ 2.20GHz GenuineIntel GNU/Linux

Version of Vim

version 8.2.814

Logs and stack traces

Error:
Vim: Caught deadly signal SEGV
Segmentation fault

USE flags:
python terminal

Plugins (vimplug):
    Plug 'turbio/bracey.vim'
    Plug 'mattn/emmet-vim'
    Plug 'hrsh7th/vim-vsnip'
    Plug 'hrsh7th/vim-vsnip-integ'
    Plug 'AlessandroYorba/Alduin'
    Plug 'valloric/youcompleteme'
    Plug 'tpope/vim-surround'
    Plug 'w0rp/ale'
    Plug 'jiangmiao/auto-pairs'
    Plug 'itchyny/lightline.vim'
    Plug 'vim-latex/vim-latex'
    Plug 'iamcco/markdown-preview.nvim', { 'do': { -> mkdp#util#install()  }, 'for': ['markdown', 'vim-plug'] }


vim --info:
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Oct 20 2021 21:53:13)
Unknown option argument: "--info"
More info with: "vim -h"

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub.
Triage notifications on the go with GitHub Mobile for iOS or Android.

TruncatedDinosour

unread,
Oct 28, 2021, 7:46:18 PM10/28/21
to vim/vim, Subscribed

also when i try to format the file it indents it double as much

TruncatedDinosour

unread,
Oct 28, 2021, 7:48:52 PM10/28/21
to vim/vim, Subscribed

and recently I have been getting "partial write" questions when trying to write (:w) in vim

lacygoill

unread,
Oct 28, 2021, 7:50:36 PM10/28/21
to vim/vim, Subscribed

Open an image on telegram (as a file)

What's telegram?

version 8.2.814

That's 17 months old. Try to reproduce on master, and without config (vim --clean or vim -Nu NONE).

also when i try to format the file it indents it double as much

and recently I have been getting "partial write" questions when trying to write (:w) in vim

Open a separate issue with enough information to reproduce.

TruncatedDinosour

unread,
Oct 28, 2021, 7:51:55 PM10/28/21
to vim/vim, Subscribed

Open an image on telegram (as a file)

What's telegram?

version 8.2.814

That's 17 months old. Try to reproduce on master, and without config (vim --clean or vim -Nu NONE).

also when i try to format the file it indents it double as much
and recently I have been getting "partial write" questions when trying to write (:w) in vim

Open a separate issue with enough information to reproduce.

It's a messaging app, I expierienced it with it so i thought maybe it's related

okay

Okay I will report it if i get it more

TruncatedDinosour

unread,
Oct 28, 2021, 7:52:41 PM10/28/21
to vim/vim, Subscribed

just got it again as i opened vim with no config:


Vim: Caught deadly signal SEGV
Segmentation fault

TruncatedDinosour

unread,
Oct 28, 2021, 7:54:28 PM10/28/21
to vim/vim, Subscribed

Managed to reproduce it with no config:

Vim: Caught deadly signal SEGV -Nu NONE
Vim: Finished.
Segmentation fault

i opened a new terminal window and it did this

TruncatedDinosour

unread,
Oct 28, 2021, 7:55:22 PM10/28/21
to vim/vim, Subscribed

I will try to reproduce it on master now

TruncatedDinosour

unread,
Oct 28, 2021, 8:05:46 PM10/28/21
to vim/vim, Subscribed

The master branch of ViM doesn't seem to weak to this bug, I will just switch to the ~amd64 keyword and it should be fine 👍

TruncatedDinosour

unread,
Oct 28, 2021, 8:05:49 PM10/28/21
to vim/vim, Subscribed

Closed #9062.

TruncatedDinosour

unread,
Oct 28, 2021, 8:09:30 PM10/28/21
to vim/vim, Subscribed

I will also add the racket USE flag as it might help :)

TruncatedDinosour

unread,
Oct 28, 2021, 8:14:48 PM10/28/21
to vim/vim, Subscribed

Actually it seems that it's not scheme's fault - it's the terminal's (:term) fault

TruncatedDinosour

unread,
Oct 28, 2021, 8:16:25 PM10/28/21
to vim/vim, Subscribed

and my youcompleteme plugin seems to have killed itself multiple times
ycmd_58391_stderr_ijozg7g8.log
ycmd_58391_stdout_i3qgbbzn.log

Dominique Pellé

unread,
Oct 29, 2021, 2:32:50 AM10/29/21
to vim/vim, Subscribed

version 8.2.814

As indicated earlier, please build the latest vim from master (currently vim-8.2.3567).
Otherwise we are likely to lose time with old bugs which are already fixed.
If this is about :term, then several crashes were fixed. I see at least these
related to crash with terminal (and maybe others):

patch 8.2.2908: crash when using a terminal popup window from cmdline window
patch 8.2.2545: errors and crash when terminal window is zero height
patch 8.2.1985: crash when closing terminal popup with <Cmd> mapping
patch 8.2.1959: crash when terminal buffer name is made empty
patch 8.2.1353: crash when drawing double-wide character in terminal window
patch 8.2.0989: crash after resizing a terminal window

TruncatedDinosour

unread,
Oct 29, 2021, 1:20:15 PM10/29/21
to vim/vim, Subscribed

Also I switched to ~amd64 kw:
/etc/portage/package.accept_keywords/vim ;

app-editors/vim ~amd64
app-editors/vim-core ~amd64

and I have added the racket USE flag to my vim build.

it helped and it seems to be fine

Reply all
Reply to author
Forward
0 new messages