[vim/vim] Segfault in version 9.2.524 (Issue #20730)

stefanos

unread,

1:53 AM (9 hours ago) 1:53 AM

to vim/vim, Subscribed

stefanos82 created an issue (vim/vim#20730)

Steps to reproduce

Run vim -V
Press Enter until it finishes with loading; it segfaults with message Segmentation fault (core dumped) vim -V; that's it.

Expected behaviour

To work normally.

Version of Vim

9.2.524

Environment

OS: Debian GNU/Linux forky/sid x86_64
Terminal: qterminal
Value of $TERM: xterm-256color
Shell: bash 5.3.9

Logs and stack traces

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.

stefanos

unread,

1:55 AM (9 hours ago) 1:55 AM

to vim/vim, Subscribed

stefanos82 left a comment (vim/vim#20730)

I have originally reported this bug in neoclide/coc.nvim#5688

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.

Maxim Kim

unread,

2:25 AM (8 hours ago) 2:25 AM

to vim/vim, Subscribed

habamax left a comment (vim/vim#20730)

Run vim -V

Press Enter until it finishes with loading; it segfaults with message Segmentation fault (core dumped) vim -V; that's it.

It is not happening here with 9.2.782. I guess information is not enough to reproduce it.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.

stefanos

unread,

5:48 AM (5 hours ago) 5:48 AM

to vim/vim, Subscribed

stefanos82 left a comment (vim/vim#20730)

This is what @fannheyward described it takes place in the aforementioned ticket I shared above:

I can reproduce this locally with Vim 9.2.0750 when using bare -V.

The crash does not appear to be caused by coc.nvim but happens inside Vim while it is building an exception stacktrace during a channel callback.

Vim is started with bare -V, so verbose output goes to the screen.

Vim enters the hit-enter prompt: Press ENTER or type command to continue.

While waiting there, Vim still processes queued channel messages.

coc.nvim receives/sends a channel callback, for example through coc#api#Call.

If that callback raises a Vim error, Vim tries to create a stacktrace.

Vim crashes in stacktrace_create() because it dereferences a NULL autocmd script context.

Use vim -V/tmp/vim-verbose.log to redirect verbose log, no segfault crashes.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.

Reply all

Reply to author

Forward