All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU 0.8.1 VNC: Segfault on closing
Date: Sun, 21 May 2006 13:26:15 -0500	[thread overview]
Message-ID: <4470B0C7.6090006@codemonkey.ws> (raw)
In-Reply-To: <Pine.LNX.4.44.0605211718440.3209-100000@zeskia.int.eridani.co.uk>

Michael McConnell wrote:
> When I try to use QEMU's VNC server, every time I close the connection it
> segfaults.  So far I've been unable to trace the cause of this (gdb appears
> to be next to useless at tracing the execution), but it is totally
> repeatable.
>   

Can you provide more information?  What VNC client are you using?  What 
host architecture are you on?  What is the guest OS/target?

Can you provide a stack trace that leads to the seg fault?

Regards,

Anthony Liguori

> Running with kqemu 1.3.0pre7 in -kernel-kqemu with Windows XP as the guest 
> operating system, the host is an Athlon XP2000+ running kernel 2.6.14, and 
> glibc 2.1.3. QEMU was compiled with gcc 3.4.3.
>
> (I tried upgrading glibc, had to restore the machine from a backup.)
>
> Any pointers would be much appreciated...
>
> -- Michael "Soruk" McConnell
>    Eridani Star System
>
>    MailStripper - http://www.MailStripper.eu/ - SMTP spam filter
>    Mail Me Anywhere - http://www.MailMeAnywhere.com/ - Mobile email
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>   

  reply	other threads:[~2006-05-21 18:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21 16:24 [Qemu-devel] QEMU 0.8.1 VNC: Segfault on closing Michael McConnell
2006-05-21 18:26 ` Anthony Liguori [this message]
2006-05-21 18:57   ` Michael McConnell
2006-05-21 23:13     ` Anthony Liguori
2006-05-21 23:43       ` Michael McConnell

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=4470B0C7.6090006@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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.