By GDB server and arm - Linux - the GDB debugger. When using the info threads thread command to display information, get the following, the function is full of question marks.

(GDB) info threads
[1523] New Thread
[1524] New Thread
[1525] New Thread
[1526] New Thread
[1527] New Thread
[1528] New Thread
[1529] New Thread
Id Target Id Frame
8 1529 0 x40120cc4 in Thread?? ()
7 1528 0 x40120cc4 in Thread?? ()
6 Thread 1527 0 x40120cc4 in?? ()
5 Thread 1526 0 x40120cc4 in?? ()
4 Thread 1525 0 x40120cc4 in?? ()
3 1524 0 x40120cc4 in Thread?? ()
2 Thread 1523 0 x40120cc4 in?? ()
* 1 1512 0 x4003b384 in Thread?? ()
(GDB)

Print a stack: inc_can1_run () as the thread function.
Bt (GDB)
# 0 can1_get_send_cmd (pT_send_cmd=0 x484cc & lt; G_t_can1_send_cmd_buff & gt; ,
PPolling_round=0 x48340 & lt; G_can1_sendPackNum & gt;) The at IncCan1Update. C: 868
# 1 0 x00012fde inc_can1_packet_send in () at IncThreadCan1. C: 113
# 2 0 x00013150 inc_can1_run in () at IncThreadCan1. C: 245
# 3 0 x40033ed2 in?? ()
# 4 0 x40033ed2 in?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(GDB)