If you had debug packages for glibc and libcrypto (libc-dbg and libssl1.0.0-dbg ?) it should show function names.
2013/11/14 André Cruz <[email protected]> > Hello. > > I sometimes see segmentation faults on the https router, which is promptly > restarted by the master process. They happen rarely, so I have no idea how > to reproduce them, and the stacktrace doesn't say very much: > > !!! uWSGI process 4818 got Segmentation Fault !!! > *** backtrace of 4818 *** > #012discoapi uWSGI http 1(uwsgi_backtrace+0x2e) [0x45ab1e] > #012discoapi uWSGI http 1(uwsgi_segfault+0x21) [0x45aca1] > #012/lib/x86_64-linux-gnu/libc.so.6(+0x324f0) [0x7f6614a534f0] > #012/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0(+0x83e4b) [0x7f6615ac3e4b] > #012*** end of backtrace *** > > > !!! uWSGI process 3689 got Segmentation Fault !!! > *** backtrace of 3689 *** > #012discoapi uWSGI http 1(uwsgi_backtrace+0x2e) [0x45ab1e] > #012discoapi uWSGI http 1(uwsgi_segfault+0x21) [0x45aca1] > #012/lib/x86_64-linux-gnu/libc.so.6(+0x324f0) [0x7f73718144f0] > #012/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0(+0x83e56) [0x7f7372884e56] > #012*** end of backtrace *** > > > !!! uWSGI process 4189 got Segmentation Fault !!! > *** backtrace of 4189 *** > #012discoapi uWSGI http 1(uwsgi_backtrace+0x2e) [0x45ab1e] > #012discoapi uWSGI http 1(uwsgi_segfault+0x21) [0x45aca1] > #012/lib/x86_64-linux-gnu/libc.so.6(+0x324f0) [0x7fd0235314f0] > #012/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0(+0x83e50) [0x7fd0245a1e50] > #012*** end of backtrace *** > > Just throwing this out there to see if someone sees the same behaviour. > This is a 1.9.15 uWSGI running on Debian 7. > > Best regards, > André > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > -- Łukasz Mierzwa
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
