JLinkGDBServer SIGSEGV (Linux)

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • JLinkGDBServer SIGSEGV (Linux)

    Hello,

    I have catched a crash of the JLinkGDBServer. Started with "JLinkGDBServer -device lpc1788 -vd -if SWD",

    "uname -a" - 3.8.0-33-generic #48~precise1-Ubuntu SMP Thu Oct 24 16:28:06 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
    "/etc/issue" - Ubuntu 12.04.3 LTS \n \l
    JLinkARM.dll V4.78j (DLL compiled Nov 22 2013 20:10:51), from the 64-bit package
    uC - LPC1788

    I have opened a second debug session accidentally to en existing previous one.

    Best Martin

    C Source Code

    1. Reading 64 bytes @ address 0x1000FFC0
    2. GDB closed TCP/IP connection
    3. GDB closed TCP/IP connection
    4. Connected to 127.0.0.1
    5. ==2269== Thread 8:
    6. ==2269== Invalid read of size 4
    7. ==2269== at 0x429918: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
    8. ==2269== by 0x403C56: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
    9. ==2269== by 0x40AEA1: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
    10. ==2269== by 0x40B56D: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
    11. ==2269== by 0x40B727: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
    12. ==2269== by 0x4E39E99: start_thread (pthread_create.c:308)
    13. ==2269== Address 0xffffffffffffffff is not stack'd, malloc'd or (recently) free'd
    14. ==2269==
    15. ==2269==
    16. ==2269== Process terminating with default action of signal 11 (SIGSEGV)
    17. ==2269== Access not within mapped region at address 0xFFFFFFFFFFFFFFFF
    18. ==2269== at 0x429918: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
    19. ==2269== by 0x403C56: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
    20. ==2269== by 0x40AEA1: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
    21. ==2269== by 0x40B56D: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
    22. ==2269== by 0x40B727: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
    23. ==2269== by 0x4E39E99: start_thread (pthread_create.c:308)
    24. ==2269== If you believe this happened as a result of a stack
    25. ==2269== overflow in your program's main thread (unlikely but
    26. ==2269== possible), you can try to increase the size of the
    27. ==2269== main thread stack using the --main-stacksize= flag.
    28. ==2269== The main thread stack size used in this run was 8388608.
    29. ==2269==
    30. ==2269== HEAP SUMMARY:
    31. ==2269== in use at exit: 5,913,034 bytes in 32 blocks
    32. ==2269== total heap usage: 9,235 allocs, 9,203 frees, 30,343,488 bytes allocated
    33. ==2269==
    34. ==2269== LEAK SUMMARY:
    35. ==2269== definitely lost: 0 bytes in 0 blocks
    36. ==2269== indirectly lost: 0 bytes in 0 blocks
    37. ==2269== possibly lost: 2,176 bytes in 8 blocks
    38. ==2269== still reachable: 5,910,858 bytes in 24 blocks
    39. ==2269== suppressed: 0 bytes in 0 blocks
    40. ==2269== Rerun with --leak-check=full to see details of leaked memory
    41. ==2269==
    42. ==2269== For counts of detected and suppressed errors, rerun with: -v
    43. ==2269== Use --track-origins=yes to see where uninitialised values come from
    44. ==2269== ERROR SUMMARY: 123427 errors from 17 contexts (suppressed: 2 from 2)
    45. Killed
    Display All