From: Ulrich Obergfell <uobergfe@redhat.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vnc: segmentation fault caused by incorrect 'bytes' count calculated in tight_compress_data()
Date: Mon, 21 Mar 2011 06:32:39 -0400 (EDT) [thread overview]
Message-ID: <584272124.436780.1300703559672.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <AANLkTimqxOWoUdE9defQG=XvQqDvMjgEyYy4t1aJxMYV@mail.gmail.com>
> Hi Ulrich,
> Looks a lot like "vnc: tight: Fix crash after 2GB of output", right ?
>
> --
> Corentin Chary
> http://xf.iksaif.net
Hi Corentin,
yes, this appears to be the same issue as:
http://lists.gnu.org/archive/html/qemu-devel/2011-03/msg02044.html
You posted your patch only a few minutes before I posted mine.
Hence, I wasn't aware that a fix was already available.
Regards,
Uli
prev parent reply other threads:[~2011-03-21 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1753565547.435765.1300696715736.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2011-03-21 8:48 ` [Qemu-devel] [PATCH] vnc: segmentation fault caused by incorrect 'bytes' count calculated in tight_compress_data() Ulrich Obergfell
2011-03-21 8:54 ` Corentin Chary
2011-03-21 10:32 ` Ulrich Obergfell [this message]
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=584272124.436780.1300703559672.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com \
--to=uobergfe@redhat.com \
--cc=corentin.chary@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).