On 2/5/07, Andrew J. Barr <[EMAIL PROTECTED]> wrote: > On Mon, 2007-02-05 at 19:45 +0100, Gwenole Beauchesne wrote: > > Hi, > > > > > It seems to be segfaulting a lot on me...although it seems to run OK > > > for at least a while. In fact, according to dmesg it is crashing with > > > signal 6 (SIGABRT). Any ideas as to what is causing this? > > > > It could be an explicit abort() or an uncaught C++ exception (which I > > doubt vbox is using). Could you detail under which conditions you get > > the crash (e.g. which OS guest, what lead to the crash, etc.)? Besides, > > an interesting x86_64 kernel feature is that it also prints the RIP for > > such crashes. So you could simply use it in gdb (or addrline?) to get > > the sources location, provided you kept the debug symbols. > > The crash seems to happen (reliably) after a certain amount of time. No > idea what is causing it, but a backtrace is below. I have seen this > reproducibly happen with both WinXP and Debian Etch guests, but this > particular trace is from an XP SP2 guest. > > Program received signal SIGSEGV, Segmentation fault. > 0x00002b380c44cdde in __lll_mutex_timedlock_wait () > from /lib/libpthread.so.0 > (gdb) where > #0 0x00002b380c44cdde in __lll_mutex_timedlock_wait () > from /lib/libpthread.so.0 > #1 0x00002b380c449ae1 in _L_mutex_timedlock_55 () > from /lib/libpthread.so.0 > #2 0x00002b380c449366 in pthread_mutex_timedlock () > from /lib/libpthread.so.0 > #3 0x00002b380c596a3e in rtSemEventWait (EventSem=0x6f2f80, > cMillies=2, > fAutoResume=true) > > at > /home/andrew/documents/src/vbox/src/VBox/Runtime/r3/posix/sems-posix.cpp:395 > #4 0x00002b380c92abf1 in VMR3WaitHalted (pVM=0x2aaaababf000, > fIgnoreInterrupts=176) > at /home/andrew/documents/src/vbox/src/VBox/VMM/VMEmt.cpp:366 > #5 0x00002b380c947fa1 in EMR3ExecuteVM (pVM=0x2aaaababf000) > at /home/andrew/documents/src/vbox/src/VBox/VMM/EM.cpp:3418 > #6 0x00002b380c92a9f0 in vmR3EmulationThread (ThreadSelf=0x6b91a0, > pvArgs=0x1e7cb0) > at /home/andrew/documents/src/vbox/src/VBox/VMM/VMEmt.cpp:137 > #7 0x00002b380c58d9c4 in rtThreadMain (pThread=0x6b91a0, > NativeThread=1998000) > at /home/andrew/documents/src/vbox/src/VBox/Runtime/thread.cpp:592 > #8 0x00002b380c59778a in rtThreadNativeMain (pvArgs=0x0) > > at > /home/andrew/documents/src/vbox/src/VBox/Runtime/r3/posix/thread-posix.cpp:136 > #9 0x00002b380c4464a5 in start_thread () from /lib/libpthread.so.0 > #10 0x00002b380d4483fd in clone () from /lib/libc.so.6 > ---Type <return> to continue, or q <return> to quit--- > #11 0x0000000000000000 in ?? ()
Just reproduced this when restarting Windows after installing some updates. Exact same stack trace. Regards, Andrew Barr > Side question: > > Should we move this discussion to vbox-devel? Perhaps this list has > people more interested in what is going on here... > > Andrew > > > Regards, > > Gwenolé. > _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
