In article <[email protected]>, Paul Ripke <[email protected]> wrote: >Not sure if it's worth logging or not, but I just had 'vi -r' segv. >System is amd64, NetBSD 9.3_STABLE (SLAVE) #15: Sat Sep 17 23:12:17 AEST 2022 > >Core was generated by `vi'. >Program terminated with signal SIGSEGV, Segmentation fault. >#0 0x00007936f95693d4 in ?? () from /lib/libc.so.12 >(gdb) bt >#0 0x00007936f95693d4 in ?? () from /lib/libc.so.12 >#1 0x00007936f954a403 in mbrtowc_l () from /lib/libc.so.12 >#2 0x00000001cd40edba in default_char2int.isra () >#3 0x00000001cd4518d3 in db_get () >#4 0x00000001cd447c5f in vs_columns () >#5 0x00000001cd447df9 in vs_screens () >#6 0x00000001cd44850e in vs_sm_next () >#7 0x00000001cd449891 in vs_sm_fill () >#8 0x00000001cd446019 in vs_paint () >#9 0x00000001cd447730 in vs_refresh () >#10 0x00000001cd445d86 in vs_resolve () >#11 0x00000001cd442916 in vi () >#12 0x00000001cd42bb26 in editor () >#13 0x00000001cd4537ef in main () > >Worth logging?
I don't see any changes that could have fixed it... But if you can reproduce it with symbols, it would be more useful... christos
