Opened 17 years ago
Closed 16 years ago
#1257 closed defect (fixed)
VBoxSDL segfaults during startup, slow ssh connections
Reported by: | Christopher | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 1.5.6 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
Dear VirtualBox team. It seems, that somehow I'm attractive for segfaults. Anyway, here are the problem descriptions:
Host: openSUSE-10.3 + all Patches, Athlon64 in 32-bit mode, kernel-default-2.6.22.9, glibc-2.6.1
Guest: WindowsXP SP2 + all patches, German, guest-additions-1.5.6 installed
Binary: VirtualBox-1.5.6_28266_openSUSE103-1.i586.rpm
SGID-vboxusers: VBoxSDL is started with SGID-vboxusers wrapper
Problem-1: If I call VBoxSDL over an ssh-forwarded (-X and -Y tested) and rather slow TDSL-cable connection (2 MBit), it segfaults always:
my-laptop@home -> ssh -> computer@uni -> VBoxSDL ==> segfault
I admit, that this is much to slow to work with. But I was just curious. If I call VBoxSDL from the same computer over a fast ssh-connection, I do not get any segfaults:
my-laptop@uni -> ssh -> computer@uni -> VBoxSDL ==> NO-segfault
Core dumps and segfaults of three VBoxSDL calls:
http://rapidshare.de/files/38689424/core.5098.during-startup-over-ssh.dat.bz2.html http://rapidshare.de/files/38689429/core.5098.during-startup-over-ssh.VBox.log.html http://rapidshare.de/files/38689434/core.5354.during-startup-over-ssh.dat.bz2.html http://rapidshare.de/files/38689437/core.5354.during-startup-over-ssh.VBox.log.html http://rapidshare.de/files/38689443/core.6749.during-startup-over-ssh-Y.dat.bz2.html http://rapidshare.de/files/38689447/core.6749.during-startup-over-ssh-Y.VBox.log.html
Problem-2: I had once and only once a direct VBoxSDL core dump, e.g. started without ssh from a terminal window. Here is the core-dump (unfortunately without log):
http://rapidshare.de/files/38689515/core.9483.bz2.html
Maybe the problems are connected.
Many thanks for your help and your good work.
Best regards
Change History (2)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if the problem still persists. There was a bugfix in version 1.6.4 which could solve this problem.
Please could you check if the recent version 1.6.2 works? If not, please could you provide another core dump for 1.6.2?