I'm on iMX7D, FreeRTOS v8, Segger J-Link package 6.30k
I got this problem happens too often when I try to start the debug session, making me retry many times .
After code upload & some initial setup (like register read, bkpts, ), the GDBServer app crashes/segfaults, and dumps core. (emailed to Segger .. )
From the traces on the system, and from the fact that disabling the RTOS library loading from GDBServer command line (remove -rtos) results in the problem going away . .(at least I haven't caught it without the plugin), I think it's the FreeRTOS plugin.
The system trace looks like:
May 06 12:31:59 systemd-coredump[3187]: Process 3142 (JLinkGDBServerC) of user 1000 dumped core.
Stack trace of thread 3178:
#0 0x00007f05c95a2624 __memset_avx2_unaligned_erms (libc.so.6)
#1 0x00007f05bd5f9b70 RTOS_UpdateThreads (RTOSPlugin_FreeRTOS.so)
#2 0x00000000004075b7 n/a (JLinkGDBServerCLExe)
#3 0x000000000040bdb1 n/a (JLinkGDBServerCLExe)
#4 0x00007f05ca0f250b start_thread (libpthread.so.0)
#5 0x00007f05c954116f __clone (libc.so.6)
Stack trace of thread 3142:
#0 0x00007f05c950f460 __nanosleep (libc.so.6)
#1 0x00007f05c9539434 usleep (libc.so.6)
#2 0x000000000040dfea n/a (JLinkGDBServerCLExe)
#3 0x00007f05c946cf2a __libc_start_main (libc.so.6)
#4 0x00000000004024c9 n/a (JLinkGDBServerCLExe)
-- Subject: Process 3142 (JLinkGDBServerC) dumped core
The last trace from JLinkGDBServer before it segfaults is Breakpoint reached ( = which is first breakpoint set, in system Reset_Handler), and then bang it's dead. The messages from -log don't show to me anything I can flag, but I don't know what to look for it in it..
I attached those two text file traces.
I had more than one crash with dump all end up to FreeRTOS plugin call (see stack trace above).
I got this problem happens too often when I try to start the debug session, making me retry many times .
After code upload & some initial setup (like register read, bkpts, ), the GDBServer app crashes/segfaults, and dumps core. (emailed to Segger .. )
From the traces on the system, and from the fact that disabling the RTOS library loading from GDBServer command line (remove -rtos) results in the problem going away . .(at least I haven't caught it without the plugin), I think it's the FreeRTOS plugin.
The system trace looks like:
May 06 12:31:59 systemd-coredump[3187]: Process 3142 (JLinkGDBServerC) of user 1000 dumped core.
Stack trace of thread 3178:
#0 0x00007f05c95a2624 __memset_avx2_unaligned_erms (libc.so.6)
#1 0x00007f05bd5f9b70 RTOS_UpdateThreads (RTOSPlugin_FreeRTOS.so)
#2 0x00000000004075b7 n/a (JLinkGDBServerCLExe)
#3 0x000000000040bdb1 n/a (JLinkGDBServerCLExe)
#4 0x00007f05ca0f250b start_thread (libpthread.so.0)
#5 0x00007f05c954116f __clone (libc.so.6)
Stack trace of thread 3142:
#0 0x00007f05c950f460 __nanosleep (libc.so.6)
#1 0x00007f05c9539434 usleep (libc.so.6)
#2 0x000000000040dfea n/a (JLinkGDBServerCLExe)
#3 0x00007f05c946cf2a __libc_start_main (libc.so.6)
#4 0x00000000004024c9 n/a (JLinkGDBServerCLExe)
-- Subject: Process 3142 (JLinkGDBServerC) dumped core
The last trace from JLinkGDBServer before it segfaults is Breakpoint reached ( = which is first breakpoint set, in system Reset_Handler), and then bang it's dead. The messages from -log don't show to me anything I can flag, but I don't know what to look for it in it..
I attached those two text file traces.
I had more than one crash with dump all end up to FreeRTOS plugin call (see stack trace above).