[vbox-dev] One more nasty stuck/crash of Qt GUI on Windows host

Huihong Luo huisinro at yahoo.com
Tue Jul 27 11:00:01 PDT 2010

when something is freezing, usually indicates some kind of loop, or inter locking of some threads.
If you attach a debugger to the process, then click Break All, it will most likely break into the place that is looping, or wait.
You can download WinDbg, a very good debugger on Windows.
One problem is that since VBox does not ship debugging symbols, you may need to build your own OSE code, which will generates debug symbol files.

--- On Tue, 7/27/10, Alexey Eremenko <al4321 at gmail.com> wrote:

From: Alexey Eremenko <al4321 at gmail.com>
Subject: Re: [vbox-dev] One more nasty stuck/crash of Qt GUI on Windows host
To: "VirtualBox developer's list" <vbox-dev at virtualbox.org>
Date: Tuesday, July 27, 2010, 10:43 AM

On Tue, Jul 27, 2010 at 8:07 AM, Alexey Eremenko <al4321 at gmail.com> wrote:
> Since we are speaking about stability as of late, I would like to
> point a problem.
> Basically, when doing copy/paste in the VBox Qt GUI on Windows host,
> in some cases the VBox GUI stucks until gets manually killed.
> This happens even if no VMs are running at all. Qt somehow manages to
> corrupt the clipboard on copy operation, then later crash on paste
> operation.
> http://www.virtualbox.org/ticket/4491
> --
> -Alexey Eromenko "Technologov"

How can we debug it ???

Can you setup some computer with remote access to it + debugging
tools, so I can reproduce the crash ?

-Alexey Eromenko "Technologov"

vbox-dev mailing list
vbox-dev at virtualbox.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.virtualbox.org/pipermail/vbox-dev/attachments/20100727/45b1800c/attachment-0001.html 

More information about the vbox-dev mailing list