Opened 13 years ago
Closed 12 years ago
#11016 closed defect (fixed)
Virtualbox crash
| Reported by: | JohnCC | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.2.0 |
| Keywords: | crash | Cc: | |
| Guest type: | other | Host type: | other |
Description
I left my VM running overnight. The guest is Win 7 64 bit, and the host is Archlinux 64 bit. When I came in this morning, there was a message saying the VM had been halted due to a critical error.
Attachments (2)
Change History (8)
by , 13 years ago
by , 13 years ago
| Attachment: | VBox.png.1 added |
|---|
comment:1 by , 13 years ago
Debugging this problem is a difficult for us because this is a custom build. Can you reproduce this crash or do you still have a core dump available? If so, open the core dump with gdb and enter 'bt'. The output would be interesting.
comment:2 by , 13 years ago
How can I actually create a core dump? One does not seem to be generated automatically. If I select "Ignore" at the error, I could attach gdb to the vbox processes and get a backtrace, but I'm not sure which one to attach to and how useful it would even be.
I should add that the crash just happened again while I was watching it, so while I cannot repeat it at will, it's not a one-off either.
UPDATE: found the docs on making core dumps so will try that next time there's a crash.
comment:3 by , 13 years ago
Just happened again, so I could probably figure out how to provoke it with a bit of luck.
comment:6 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with VBox 4.2.4 and you can provide a core dump.
Log file