Received signal 11 (SIGSEGV)

Help
Brad Chin
2012-11-15
2013-06-12
  • Brad Chin

    Brad Chin - 2012-11-15

    My staf v3.4.1 with stax v3.4.5 crashed on my Fedora 9.

    This seems to be the only info I got from the stdout logs:

    20121115-10:24:36;139943678331216;00000100;Received signal 11 (SIGSEGV)
    20121115-10:24:36;139943678331216;00000100;Received signal 6 (SIGABRT)

    Is there any other place where I can find out what happened?

    I restarted staf with tracepoints info and warning. Is there something else I can do?

    Thanks,
    Brad

     
  • Sharon Lucas

    Sharon Lucas - 2012-11-15

    You should upgrade STAF to V3.4.11 (you are 10 releases behind) in case this issue has already been resolved.  Post again if the problem still occurs after upgrading STAF to the current version.

    If it generated a core dump when STAFProc encountered a SIGSEGV then you could use gdb to look at the core file.  However, unless you  are running a debug version of STAF (e.g. if you build STAF yourself with BUILD_TYPE=debug), you won't get a whole lot of useful information from the core dump except for the number of threads running.

     
  • Brad Chin

    Brad Chin - 2012-11-15

    How can I determine or find the BUILD_TYPE? Do I need to compile staf myself with build_type=debug, if I want the debug version?

    Thanks,
    Brad 

     
  • Sharon Lucas

    Sharon Lucas - 2012-11-16

    We only provide STAF binaries in non-debug (aka retail) on the http://staf.sourceforge.net website.  You would need to compile STAF yourself from source code following the instructions in the STAF Developer's Guide at http://staf.sourceforge.net/current/stafdg.html and setting environment variable BUILD_TYPE=debug instead of its default value of retail (e.g. export BUILD_TYPE=debug.  But, before you go to the trouble of building it, you may want to upgrade to STAF V3.4.11 as the problem may no longer exist.

     
  • Brad Chin

    Brad Chin - 2012-11-16

    okay, thank you very much. I have upgraded.

     

Log in to post a comment.