VirtualBox

Ticket #1993 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

segmentation fault - AMD64 - Gentoo - 1.6.4

Reported by: TioBorracho Owned by:
Priority: major Component: other
Version: VirtualBox 1.6.4 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description

I'm getting these seg.faults often.

The last oe with this message VBoxSVC[8884]: segfault at 8 ip 7fbbefd6d4a0 sp 7ffff9b8b620 error 4 in VBoxXPCOMIPCC.so[7fbbefd51000+28000]

If you need further information about my system I will add it.

Change History

comment:1 Changed 6 years ago by frank

Is this the OSE version or the PUEL version? How do you reproduce the SEGFAULT, that is, are you doing something special?

Can you provide us a core dump ( http://www.virtualbox.org/wiki/Core_dump)? Regarding the core dump you could send me a private E-mail to frank _dot_ mehnert at sun _dot_ com.

comment:2 follow-up: ↓ 5 Changed 6 years ago by TioBorracho

OSE Version. I don't really have a method to reproduce the segfault, but it generally happens when doing a lot of disk write access or processing. Yesterday it was exporting a project with audacity on a samba share from win-virtual to host-samba. Today it happenned while importing photos from a samba-share on the host from win-virtual with Lightroom... I wess it might have something to do with net-access and samba perhaps?

I will run it with core dumping tomorrow.

comment:3 Changed 6 years ago by frank

Yes, please try to reproduce the bug. And make sure that you installed the debug package of VirtualBox, I hope that Gentoo provides such a package. Then, open the core dump with

gdb -c core /usr/lib/virtualbox/VBoxSVC

(probably you need to adapt the path -- I don't know the Gentoo layout). Make sure that gdb can access all debug symbols, so read the gdb messages. If it cannot load some libraries symbols, make sure to install the corresponding debug symbols package (libc, VirtualBox).

comment:4 Changed 6 years ago by TioBorracho

Mmmm..... I don't see any particular package or use keyword that make me think about debug options of virtualbox (I'm using virtualbox-bin package so I can get USB, not the open source version, I wrote it wrong in the previous message)

comment:5 in reply to: ↑ 2 Changed 6 years ago by TioBorracho

Replying to TioBorracho:

OSE Version.

PUEL version, sorry about the confusion.

comment:6 Changed 6 years ago by frank

So you are using the PUEL version and we have the debug symbols available. So a core dump would be appreciated.

comment:7 Changed 6 years ago by TioBorracho

If I ran VBox with a desktop shortcut with this command where should the core file be?

VBoxManage startvm "Windows prueba"

comment:8 Changed 6 years ago by TioBorracho

I ran Virtualbox calling it from a consolre but no core dump was created.

I followed the indicacion to make ulimit inlimited...

comment:9 Changed 6 years ago by frank

The core dump is created in the directory where you started the VM from. So if there is no core dump after the VBoxManage command crashed, something is wrong with your ulimit. You also should ensure that ulimit was not previously decreased by some start script (e.g. .bashrc).

comment:10 Changed 6 years ago by frank

Please could you check if 1.6.6 fixes the problem for you?

comment:11 follow-up: ↓ 12 Changed 6 years ago by TioBorracho

Well, I installed 2.0 now and so far, so good, no new crashes.

comment:12 in reply to: ↑ 11 Changed 6 years ago by TioBorracho

Replying to TioBorracho:

Well, I installed 2.0 now and so far, so good, no new crashes.

Sorry, 1.6.6, but no crahse yet

comment:13 Changed 6 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

So I consider this bug as fixed, please reopen if necessary.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use