shellinaboxd core dumps on signal 11 after unknown error

Question

From mnsli....com on October 13, 2010 21:16:32

We're running shellinabox with the following arguments:

/usr/local/bin/shellinaboxd -b -p 4200 --css=white-on-black.css --css=siab.css -t --disable-ssl-menu

This is running on FreeBSD 7.1-RELEASE and runs for a fairly long time, then seems to randomly core dump. I am not finding any cores, but are there some debug options I can enable to perhaps track this down? Typically, we'll have about 15 different sessions at a give time on each server.

Original issue: http://code.google.com/p/shellinabox/issues/detail?id=94

该提问来源于开源项目：shellinabox/shellinabox

Answer 1

From zod....com on October 13, 2010 16:55:43

Is this with the top of the tree in Subversion, or are you running the pre-packaged version? I recently fixed a bug that was triggered by newer versions of gcc and that could result in an occasional segmentation fault.

Other than that, yes, core files would be very useful. ShellInABox deliberately disables core files, as there is a small risk that they could included security-sensitive data (e.g. user passwords).

You can edit the main() function in shellinabox/shellinaboxd.c. At the very top of it, there is a call to prctl() and a little further down a call to setrlimit(RLIMIT_CORE). Comment both of these lines out, and you should again be able to get core files.