Opened 16 years ago
Closed 16 years ago
#1993 closed defect (fixed)
segmentation fault - AMD64 - Gentoo - 1.6.4
| Reported by: | Dario | Owned by: | |
|---|---|---|---|
| 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 (13)
comment:1 by , 16 years ago
follow-up: 5 comment:2 by , 16 years ago
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 by , 16 years ago
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 by , 16 years ago
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 by , 16 years ago
comment:6 by , 16 years ago
So you are using the PUEL version and we have the debug symbols available. So a core dump would be appreciated.
comment:7 by , 16 years ago
If I ran VBox with a desktop shortcut with this command where should the core file be?
VBoxManage startvm "Windows prueba"
comment:8 by , 16 years ago
I ran Virtualbox calling it from a consolre but no core dump was created.
I followed the indicacion to make ulimit inlimited...
comment:9 by , 16 years ago
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).
follow-up: 12 comment:11 by , 16 years ago
Well, I installed 2.0 now and so far, so good, no new crashes.
comment:12 by , 16 years ago
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 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
So I consider this bug as fixed, please reopen if necessary.
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.