Bram is right, the message is processed too early. Sorry, I was an idiot.
This can be fixed with:
diff --git a/src/if_xcmdsrv.c b/src/if_xcmdsrv.c
index cf6d9a7..b1fbdaa 100644
--- a/src/if_xcmdsrv.c
+++ b/src/if_xcmdsrv.c
@@ -1235,9 +1235,9 @@ server_parse_messages()
while (head.next != NULL && head.next != &head)
{
node = head.next;
- server_parse_message(X_DISPLAY, node->propInfo, node->len);
head.next = node->next;
node->next->prev = node->prev;
+ server_parse_message(X_DISPLAY, node->propInfo, node->len);
vim_free(node);
}
}
On Sunday, October 4, 2015 at 4:35:15 PM UTC-4, Karl Yngve Lervåg wrote:
> I think you are right, @chrisbra (and hi, btw!). I've compiled vim from
> source, and I find that the test works as expected in patch 865, and as you
> guessed it fails (and crashes) in patch 866. I will leave it to you or
> @brammool (or someone else) to figure out the correct way to solve the issue,
> as it seems far beyond my poor C skills to determine the cause of the error.
>
>
> —
> Reply to this email directly or view it on GitHub.
--
--
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].
For more options, visit https://groups.google.com/d/optout.