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
Reading 64 bytes @ address 0x1000FFC0
GDB closed TCP/IP connection
GDB closed TCP/IP connection
Connected to 127.0.0.1
==2269== Thread 8:
==2269== Invalid read of size 4
==2269== at 0x429918: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
==2269== by 0x403C56: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
==2269== by 0x40AEA1: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
==2269== by 0x40B56D: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
==2269== by 0x40B727: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
==2269== by 0x4E39E99: start_thread (pthread_create.c:308)
==2269== Address 0xffffffffffffffff is not stack'd, malloc'd or (recently) free'd
==2269==
==2269==
==2269== Process terminating with default action of signal 11 (SIGSEGV)
==2269== Access not within mapped region at address 0xFFFFFFFFFFFFFFFF
==2269== at 0x429918: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
==2269== by 0x403C56: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
==2269== by 0x40AEA1: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
==2269== by 0x40B56D: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
==2269== by 0x40B727: ??? (in /opt/SEGGER/JLink/JLinkGDBServer)
==2269== by 0x4E39E99: start_thread (pthread_create.c:308)
==2269== If you believe this happened as a result of a stack
==2269== overflow in your program's main thread (unlikely but
==2269== possible), you can try to increase the size of the
==2269== main thread stack using the --main-stacksize= flag.
==2269== The main thread stack size used in this run was 8388608.
==2269==
==2269== HEAP SUMMARY:
==2269== in use at exit: 5,913,034 bytes in 32 blocks
==2269== total heap usage: 9,235 allocs, 9,203 frees, 30,343,488 bytes allocated
==2269==
==2269== LEAK SUMMARY:
==2269== definitely lost: 0 bytes in 0 blocks
==2269== indirectly lost: 0 bytes in 0 blocks
==2269== possibly lost: 2,176 bytes in 8 blocks
==2269== still reachable: 5,910,858 bytes in 24 blocks
==2269== suppressed: 0 bytes in 0 blocks
==2269== Rerun with --leak-check=full to see details of leaked memory
==2269==
==2269== For counts of detected and suppressed errors, rerun with: -v
==2269== Use --track-origins=yes to see where uninitialised values come from
==2269== ERROR SUMMARY: 123427 errors from 17 contexts (suppressed: 2 from 2)
Killed