It looks like you have a custom component that's maybe doing something bad 
inside a timer handler?  I'd start inspecting there (e.g., by disabling 
timers...).

-- Murphy

On Oct 23, 2010, at 12:12 PM, Nikhil Handigol wrote:

> My NOX controller seems to be segfaulting quite a bit of late. What is the 
> best way to figure out the cause of the crash from the dump?
> 
> Here's the segfault dump:
> 
> Caught signal 11.
>   0xb7d8a169   64 (vigil::fault_handler(int)+0x49)
>   0xb7fa0400 2894416736 (__kernel_sigreturn+0x0)
>   0xb3b907bb   16 
> (boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, 
> boost::_mfi::mf0<void, vigil::ClientMan>, 
> boost::_bi::list1<boost::_bi::value<vigil::ClientMan*> > >, 
> void>::invoke(boost::detail::function::function_buffer&)+0x1b)
>   0xb7dd6110 2544 (vigil::Timer_dispatcher::poll()+0x480)
>   0xb7db1529
>   0xb7db1cbf
>   0xb7dae975
>   0xb7dcb07f  112 (boost::function0<void>::operator()() const+0x2f)
>   0xb7dc5d30
>   0xb7aa8955
> Segmentation fault
> 
> 
> Thanks,
> Nikhil
> _______________________________________________
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org


_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Reply via email to