All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>,
	Anthony Liguori <aliguori@us.ibm.com>
Subject: [Qemu-devel] [BUG] [PATCH] [STABLE] Fix monitor command (screendump)
Date: Tue, 24 Mar 2009 22:42:58 +0100	[thread overview]
Message-ID: <49C953E2.8090702@mail.berlios.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 463 bytes --]

Hello,

starting with r6839, the monitor command 'screendump'
raises a nullpointer memory access which crashs Qemu.

My patch fixes this for trunk and for the stable branch.

Regards

Stefan

PS. There are a lot of unapplied patches (not only from me)
which really should be applied to trunk. Much time and efforts
are wasted for maintaining local patch trees, some fixes
are sent 3 times by different people. How can we improve
this insatisfying situation?






[-- Attachment #2: screendump.patch --]
[-- Type: text/x-diff, Size: 673 bytes --]

Fix crash when calling screendump from monitor.

This was a regression introduced with r6839:
DisplayAllocator interface (Stefano Stabellini)

Signed-off-by: Stefan Weil <weil@mail.berlios.de>

Index: trunk/hw/vga.c
===================================================================
--- trunk.orig/hw/vga.c	2009-03-24 19:35:00.000000000 +0100
+++ trunk/hw/vga.c	2009-03-24 19:37:56.000000000 +0100
@@ -2637,6 +2637,7 @@
     dcl.dpy_resize = vga_save_dpy_resize;
     dcl.dpy_refresh = vga_save_dpy_refresh;
     register_displaychangelistener(ds, &dcl);
+    ds->allocator = &default_allocator;
     ds->surface = qemu_create_displaysurface(ds, w, h);
 
     s->ds = ds;

             reply	other threads:[~2009-03-24 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 21:42 Stefan Weil [this message]
2009-03-24 21:47 ` [Qemu-devel] [BUG] [PATCH] [STABLE] Fix monitor command (screendump) Anthony Liguori
2009-03-24 22:31 ` Ryan Harper
2009-03-25 10:27 ` Stefano Stabellini
2009-03-28 17:29 ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49C953E2.8090702@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.