VirtualBox crashed with SIGSEGV

Bug #1213587 reported by Cristian Aravena Romero
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Working with Centos 6.4 and Crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: virtualbox-qt 4.2.16-dfsg-1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
Date: Sun Aug 18 03:51:32 2013
ExecutablePath: /usr/lib/virtualbox/VirtualBox
InstallationDate: Installed on 2013-07-31 (17 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130724)
MarkForUpload: True
ProcCmdline: /usr/lib/virtualbox/VirtualBox --comment Centos6.4-SO_Red --startvm 52649734-f19b-4a81-80e8-71398a8d6e9a --no-startvm-errormsgbox
ProcEnviron:
 LANGUAGE=es_CL:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f011493ccb2: movzbl 0xb(%rcx),%eax
 PC (0x7f011493ccb2) ok
 source "0xb(%rcx)" (0x7f00f6f17681) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: virtualbox
StacktraceTop:
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
Title: VirtualBox crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 doanswer (pHostent=0x0, pIp=0x7f00f6f17662, pszQname=0x7f00f6f1768a <Address 0x7f00f6f1768a out of bounds>, pReqMeta=0x7f00f6f176a7, pHdr=0x7f00f6f1767e) at /build/buildd/virtualbox-4.2.16-dfsg/src/VBox/Devices/Network/slirp/libalias/alias_dns.c:107
 protohandler (la=0x7f010c505770, pIp=0x7f00f6f17662, ah=<optimized out>) at /build/buildd/virtualbox-4.2.16-dfsg/src/VBox/Devices/Network/slirp/libalias/alias_dns.c:254
 UdpAliasIn (pip=0x7f00f6f17662, la=0x7f010c505770) at /build/buildd/virtualbox-4.2.16-dfsg/src/VBox/Devices/Network/slirp/libalias/alias.c:769
 LibAliasInLocked (la=0x7f010c505770, ptr=0x7f00f6f17662 <Address 0x7f00f6f17662 out of bounds>, maxpacketsize=<optimized out>) at /build/buildd/virtualbox-4.2.16-dfsg/src/VBox/Devices/Network/slirp/libalias/alias.c:1282
 ip_input (pData=pData@entry=0x7f010c502820, m=m@entry=0x7f00f6ffafc4) at /build/buildd/virtualbox-4.2.16-dfsg/src/VBox/Devices/Network/slirp/ip_input.c:121

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in virtualbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.