Message ID | 1403783111-28592-1-git-send-email-batuzovk@ispras.ru |
---|---|
State | New |
Headers | show |
Il 26/06/2014 13:45, Kirill Batuzov ha scritto: > chr_write_lock was introduced in commit 9005b2a7589540a3733b3abdcfbccfe7746cd1a1 > but was used uninitialized. It caused segmentation fault on windows hosts. A similar patch is already on the list. Thanks anyway for your contribution! Paolo
diff --git a/qemu-char.c b/qemu-char.c index 2e50a10..17bd360 100644 --- a/qemu-char.c +++ b/qemu-char.c @@ -94,6 +94,7 @@ static QTAILQ_HEAD(CharDriverStateHead, CharDriverState) chardevs = CharDriverState *qemu_chr_alloc(void) { CharDriverState *chr = g_malloc0(sizeof(CharDriverState)); + qemu_mutex_init(&chr->chr_write_lock); return chr; }