#1611 closed defect (fixed)
VBoxHeadless w/ VRDP segfault when entering => Retry with 1.6.6
| Reported by: | Cedric Vivier | Owned by: | |
|---|---|---|---|
| Component: | RDP | Version: | VirtualBox 1.6.0 |
| Keywords: | vrdp headless | Cc: | vbox@… |
| Guest type: | other | Host type: | other |
Description
On Linux 64-bit tar.gz VirtualBox 1.6.0 setup.
On a Windows XP guest, whenever I enter "Add/remove components" from the "Add/remove programs" control panel, VRDP makes the headless session crash :
VBoxHeadless[5435]: segfault at 4 ip 7fcf9c5ed0dc sp 410f8b90 error 4 in VBoxVRDP.so[7fcf9c59e000+8e000]
Change History (10)
follow-up: 3 comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Component: | other → RDP |
|---|
comment:3 by , 17 years ago
Replying to frank:
We fixed some similar bugs after 1.6.2 was released. If you like we could provide you a test build so you could verify that your bug was actually fixed.
I have the same problem. The VM crashes any time when using it via RDP. Is it possible to get such a test build? Maybe it helps...
comment:4 by , 16 years ago
To all of you: Could you provide a core dump (http://www.virtualbox.org/wiki/Core_dump)?
comment:5 by , 16 years ago
Having similar issues when trying to run headless. Attached is the core dump. Running Fedora 8 x86 32-bit with VirtualBox-1.6.4_33808_fedora8-1.i586.rpm
comment:7 by , 16 years ago
Got it but unfortunately, some symbol addresses seem to be changed. I suggest you to wait for 1.6.6 which should be available these days and try if the bug was already fixed.
comment:8 by , 16 years ago
| Summary: | VBoxHeadless w/ VRDP segfault when entering → VBoxHeadless w/ VRDP segfault when entering => Retry with 1.6.6 |
|---|
Please retry with 1.6.6 which is now available for download.
comment:9 by , 16 years ago
Confirmed fixed under Fedora 8 VirtualBox v1.6.6. "VBoxManage startvm" does not segfault anymore. Thanks!
comment:10 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
We fixed some similar bugs after 1.6.2 was released. If you like we could provide you a test build so you could verify that your bug was actually fixed.