VirtualBox

Ticket #1049 (closed defect: fixed)

Opened 6 years ago

Last modified 5 years ago

nmap 10.0.2.2 (host machine) results in vbox crash => Fixed in 2.1.0

Reported by: nevyn Owned by:
Priority: major Component: network/NAT
Version: VirtualBox 1.5.4 Keywords: nmap crash
Cc: emanuel.schmid@… Guest type: other
Host type: other

Description

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.

Attachments

Purskul-2008-01-07-10-15-36.log Download (30.8 KB) - added by nevyn 6 years ago.
vbox log file
VirtualBox.dmp Download (38.7 KB) - added by nevyn 6 years ago.
minidump via visual studio debugger
4a13_appcompat.txt Download (21.1 KB) - added by Fackamato 6 years ago.
Windows Error Report Contents
VBox.log Download (63.0 KB) - added by Fackamato 6 years ago.
Virtualbox logfile

Change History

Changed 6 years ago by nevyn

vbox log file

comment:1 Changed 6 years ago by frank

Please could you provide a minidump?

comment:2 Changed 6 years ago by nevyn

I guess I can - but sorry, I don't know how I create it ;) Can you give me a short pointer here? Google, friends and manuals are letting me alone on this one.

comment:3 Changed 6 years ago by frank

Have a look at  http://www.codeproject.com/KB/debug/postmortemdebug_standalone1.aspx . Minidumps should be generated by default and their location should be \windows\minidump.

Changed 6 years ago by nevyn

minidump via visual studio debugger

comment:4 Changed 6 years ago by nevyn

As I have Visual Studio installed on this machine, I used the debugger and saved the dump via Debug->Save dump. Hope this results in the same as without the studio...

The file is attached.

comment:5 Changed 6 years ago by frank

  • Component changed from other to network

comment:6 Changed 6 years ago by Fackamato

I'm experiencing what I think is the same bug. Using Virtualbox 1.6.2 on a WinXP SP2 host and lastest Frugalware XFCE beta with kernel 2.6.25-fw7. nmap is 4.68. NEtworking is NAT.

There, I just made it crash again by nmapping google.ie. Seems like it's always reproducable. I attach the Windows error report textfile, I have no idea if it's useful though.

Is there some way I can help debugging this?

Changed 6 years ago by Fackamato

Windows Error Report Contents

comment:7 Changed 6 years ago by Fackamato

Also attaching my vbox.log.

Changed 6 years ago by Fackamato

Virtualbox logfile

comment:8 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
  • Component changed from network to network/NAT
  • Summary changed from nmap 10.0.2.2 (host machine) results in vbox crash to nmap 10.0.2.2 (host machine) results in vbox crash => Fixed in 2.1.0

This was fixed in 2.1.0.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use