On Tue, Oct 31, 2023 at 1:53 PM varun bali <[email protected]> wrote:
>
> Hi,
>
> We are facing segmentation fault in vim-enhanced rpm, when we are opening two 
> or more files simultaneously from vim on same server, then if we reboot the 
> system vim generates core/crashes. Attaching gdb log for same and core file 
> for same.
> STEPS to reproduce:
> 1) open any two files simultaneously on same server using two diffrent 
> terminals of same system.
> 2) Open another 3rd terminal and do a restart there,
> 3) After restart when system is up we see vim core is generated by 
> vim-enhanced rpm for ALMALINUX8.
>
>
> Regards,
>
> Varun Bali

I agree that crashes should never happen; however, halting (or
rebooting) the machine regularly while Vim (and some other programs
including, among others, Firefox, Thunderbird and SeaMonkey) are left
running is courting disaster.

The following applies to Linux; similar procedures apply /mutatis
mutandis/ to other platforms:
Before you close down the system (other than by an unforeseen citywide
power mains blackout) I recommend to:
- quit any running instance of Vim or gvim by :qa or :xa
- quit any running browser or mailer, usually by Ctrl-Q
- quit any "risky" GUI, I don't have an exhaustive list of them
- exit (log out of) any Linux console (normally it's Ctrl-Alt-F1 to
Ctrl-Alt-F6, come back by Ctrl-Alt-F7)
- wait 5 minutes, or at least until "ps -A |less" lists no browser,
mailer or (g)vim instance
*Then* you can safely trigger a system shutdown or reboot.

Best regards,
Tony.

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAJkCKXvuzt-YjKAnPuiZkxyRoQptJ8YxJSktD7gYYKLp_05CJQ%40mail.gmail.com.

Raspunde prin e-mail lui