1. Forum
  2. Usenet
  3. COMP.OS.VXWORKS

  • Debugging Signal 11 in VxWorks7

    From lewisdo@objectcomputing.com@21:1/5 to All on Wed Nov 14 09:38:50 2018
    I'm debugging an application I've built for VxWorks7.

    I'm getting an "RTP 0xsomenumber has stopped due to signal 11".

    I read this post: https://groups.google.com/forum/#!topic/comp.os.vxworks/ZkRiaF_B5nQ

    Telling how to debug in an older version of VxWorks and I'm wondering if the same suggestions are true for VxWorks7 with all the changes that went into it.

    I'm running the application via a telnet console in Workbench 4.

    Thanks,
    Doug

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From kuhlenough@gmail.com@21:1/5 to All on Thu Sep 5 10:21:37 2019
    Signal 11 just says the program got segmentation fault, (accessed memory it shouldn't have) it is almost useless on it's own to diagnosis anything on any OS.

    Stop using telnet, it's security risk and you don't want it in your build at the end anyway, get the debugger connected and use it for what it's made for.

    Or if your a command line addict turn on ED&R and use it over SSH to get pretty back-traces and other good information.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)