vim @7.4.035_0+huge Runtime error: segfaults on yaml syntax

[vergus@…]

Running `vim -u NONE test.yaml' and then enabling syntax with ':syntax enable' results in a segfault.

This issue is not present in vim 7.4 compiled directly from the mercurial source, nor with the previous version of the port, vim @7.3.762_3+huge.

[vergus@…]

Scratch this. The runtimepath on the mercurial source wasn't properly set, once it was, it also segfaulted. Reporting this upstream to the vim-mac mailing list.

[raimue (Rainer Müller)]

Sorry, I can't reproduce this issue. The syntax highlighting for the provided test file works for me using vim @7.4.035_0+huge. Please attach any crash log that may have been produced. Check the directory ~/Library/Logs/DiagnosticReports/ for anything related to vim.

[vergus@…]

~/Library/Logs/DiagnosticReports/ was empty, so I used the instructions in the vim debug doc to create a stacktrace and sent it to Bram:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000101101aa0
0x000000010018e164 in copy_pim (to=0x101242d20, from=0x101101aa0) at regexp_nfa.c:3842
3842        to->result = from->result;
(gdb) where
#0  0x000000010018e164 in copy_pim (to=0x101242d20, from=0x101101aa0) at regexp_nfa.c:3842
#1  0x000000010018f451 in addstate (l=0x7fff5fbfe010, state=0x1008c0508, subs_arg=0x101101d50, pim=0x101101aa0, off=0) at regexp_nfa.c:4333
#2  0x000000010018f66b in addstate (l=0x7fff5fbfe010, state=0x1008c0558, subs_arg=0x101101d50, pim=0x101101aa0, off=0) at regexp_nfa.c:4366
#3  0x00000001001901ee in addstate_here (l=0x7fff5fbfe010, state=0x1008c0558, subs=0x101101d50, pim=0x101101aa0, ip=0x7fff5fbfdff4) at regexp_nfa.c:4604
#4  0x0000000100195ca1 in nfa_regmatch (prog=0x1008bf200, start=0x1008c07b0, submatch=0x7fff5fbfe458, m=0x7fff5fbfe1c8) at regexp_nfa.c:6535
#5  0x0000000100196884 in nfa_regtry (prog=0x1008bf200, col=4) at regexp_nfa.c:6709
#6  0x0000000100197099 in nfa_regexec_both (line=0x10086a7cd "  - 106.178.200.46:8080", startcol=4) at regexp_nfa.c:6893
#7  0x00000001001976ad in nfa_regexec_multi (rmp=0x7fff5fbfe990, win=0x10084e000, buf=0x10084f600, lnum=3, col=4, tm=0x0) at regexp_nfa.c:7142
#8  0x00000001001979fe in vim_regexec_multi (rmp=0x7fff5fbfe990, win=0x10084e000, buf=0x10084f600, lnum=3, col=4, tm=0x0) at regexp.c:8088
#9  0x00000001001f00db in syn_regexec (rmp=0x7fff5fbfe990, lnum=3, col=4, st=0x0) at syntax.c:3272
#10 0x00000001001ed949 in syn_current_attr (syncing=0, displaying=1, can_spell=0x0, keep_state=0) at syntax.c:2092
#11 0x00000001001ed0ba in get_syntax_attr (col=4, can_spell=0x0, keep_state=0) at syntax.c:1851
#12 0x00000001001a0a91 in win_line (wp=0x10084e000, lnum=3, startrow=2, endrow=39, nochange=1) at screen.c:4274
#13 0x000000010019bb58 in win_update (wp=0x10084e000) at screen.c:2010
#14 0x00000001001993d6 in update_screen (type=40) at screen.c:681
#15 0x0000000100231819 in main_loop (cmdwin=0, noexmode=0) at main.c:1232
#16 0x0000000100231438 in main (argc=10, argv=0x7fff5fbff590) at main.c:1020

[vergus@…]

Replying to raimue@…:

Sorry, I can't reproduce this issue. The syntax highlighting for the provided test file works for me using vim @7.4.035_0+huge. Please attach any crash log that may have been produced. Check the directory ~/Library/Logs/DiagnosticReports/ for anything related to vim.

Bram just patched it here: ​https://code.google.com/p/vim/source/detail?r=e7a2f217a385e6aebfddc4d29182924ac017d262

[raimue (Rainer Müller)]

Thanks for taking this upstream. I committed an update to vim @7.4.052_0 in r111960. Please test if this works for you with the new version.

[vergus@…]

Works great. Thanks!