Ticket #1049 (closed defect: fixed)
nmap 10.0.2.2 (host machine) results in vbox crash => Fixed in 2.1.0
|Reported by:||nevyn||Owned by:|
|Version:||VirtualBox 1.5.4||Keywords:||nmap crash|
Scanning the host machine from inside the virtual machine with "nmap 10.0.2.2" results in a crash of the virtual machine. The problem is reproducible without problem here. What feels a bit weird is the delay between the command and the crash sometimes: nmap gives its result and the command line returns, then it takes some seconds until the crash (up to about a minute). All other networking seems to work fine, including mounting a share on the host via smb.
The log file is attached, but does not contain any useful information as far as I can see (nothing about the crash in any case). Starting the microsoft visual studio debugger after the crash gives the following error: "Unhandled exception at 0x02f75b96 in VirtualBox.exe: 0xC0000005: Access violation writing location 0x06697674.". The exception address shows up again in the call stack in VBoxDD.dll. Didn't check so far, but if there is a version available with debugging symbols I might run that one again to get more information.
Ah, right: VirtualBox 1.5.4, host Windows XP w/ service pack 2 and a stupid novell netware client, guest debian etch kernel 2.6.18 (-5-686). Network adapter 0 is NAT, the others are disabled.