On Thu, 2019-08-22 at 12:30 +0300, Nadav Har'El wrote:
> Please run "osv syms" to allow gdb to find your application object
> files, and show lines there. Perhaps it's a segfault inside your
> application, not the kernel?
I had, but I had forgotten to add our stuff to the usr.manifest so the
tool could find them. I think this is better (from a different run,
apologies):
#44 <signal handler called>
#45 0x0000100005a67675 in process_main ()
#46 0x0000100005a714e9 in sched_thread_func ()
#47 0x0000100005cbab5d in thr_wrapper ()
#48 0x0000000040461c96 in
pthread_private::pthread::<lambda()>::operator() (
__closure=0xffffa0007fea4200) at libc/pthread.cc:114
#49 std::_Function_handler<void(),
pthread_private::pthread::pthread(void* (*)(void*), void*, sigset_t,
const pthread_private::thread_attr*)::<lambda()> >::_M_invoke(const
std::_Any_data &) (__functor=...) at
/usr/include/c++/7/bits/std_function.h:316
#50 0x00000000403f9647 in sched::thread_main_c (t=0xffff80007f4a3040)
at arch/x64/arch-switch.hh:271
#51 0x000000004039a793 in thread_main () at arch/x64/entry.S:113
process_main is something inside the beam/ERTS (which isn't compiled
with debug unfortunately). I'd guess its unlikely that its a bug in
there as the code is very widely tested.
Rick
--
You received this message because you are subscribed to the Google Groups "OSv
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/osv-dev/aaf2886ca999f40dc6cc8cbbf627d1b825f5fa74.camel%40rossfell.co.uk.
