Problem in vim-enahanced rpm for ALMALINUX8 causing segmentation fault.

[varun bali]

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

[Tony Mechelynck]

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.

[Tony Mechelynck]

On Wed, Nov 15, 2023 at 6:55 PM Tony Mechelynck
<antoine.m...@gmail.com> wrote:
>
> On Tue, Oct 31, 2023 at 1:53 PM varun bali <varun...@gmail.com> 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)

-- P.S. Sometimes Ctrl-Alt-F7 is an X11 login form and Ctrl-Alt-F8 is
your GUI display session.