6 Apr
2011
6 Apr
'11
7:02 a.m.
Tim, All,
Below is a backtrace and links to the full backtrace I get in Trinity
kdesktop. There may be more than 1 bug here, but it looks like at least
part of
it may be in the Trinity code. Let me know if there is something else you
think
may help isolate the issue.
OK, sorry to resurrect an old thread here, but now I am seeing the exact
same problems on my VirtualBox test machines. What I want to know, before
purchasing additional physical development hardware, is this:
*** Was anyone able to get the crash to occur *outside* of VirtualBox? ***
I ask because I'm seeing this on both Qt3 AND Qt4, in kdesktop, on two
completely different virtual machines, each running on top of a different
physical machine. It is in kdesktop, Valgrind is throwing errors on
squeaky clean code, and basically nothing makes sense. :-/
Thanks!
Tim