IMX7D gdb cannot debug application

864535720 — Sun, 22 Dec 2019 01:40:06 GMT

Hello everyone,

my development board is IMX7DSABRE, Linux version 4.1.15. The file system is burned through mfgtools.
Now I have two problems.
Question 1: When I debug a multi-threaded application on the development board, gdb prompts "warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available."
Message 1: Information when gdb starts:
root @ imx6ul7d: / qt / bin # gdb KMonitor
GNU gdb (GDB) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3 +: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-poky-linux-gnueabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word" ...
Reading symbols from KMonitor ... done.
(gdb) r
Starting program: / qt / bin / KMonitor
Cannot access memory at address 0x0
warning: Could not load shared library symbols for linux-vdso.so. 1.
Do you need "set solib-search-path" or "set sysroot"?
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
AAAAAAAAAA strUiCfgPath "config / uiconfig / k1 / common.xml"
[Debug], [Gui Thread], [11-16 09: 57: 39.725], [CAppLog.cpp, 320], Software Startup.
Message 2: When SIGINT signal is generated using Ctrl + C, gdb prints the following information:
^ C [LWP 674 exited]
[Inferior 1 (process 674) exited with code 01]
(gdb)

Question 2: For question 1, I changed the file system, and the previous warning is gone. But in the process of gdb debugging, when I use Ctrl + C to generate a SIGINT signal, my program cannot continue and can only be run again.
Information one: The information when gdb starts running:
root @ imx6qsabresd: / qt / bin # gdb KMonitor
GNU gdb (GDB) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3 +: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-poky-linux-gnueabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word" ...
Reading symbols from KMonitor ... done.
(gdb) r
Starting program: / qt / bin / KMonitor
warning: Could not load shared library symbols for linux-vdso.so. 1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0x73309410 (LWP 519)]
[Debug], [Gui Thread], [11-16 09: 46: 41.318], [CGGppLog.cpp, 320], Software Startup.

Message 2: When SIGINT signal is generated using Ctrl + C, gdb prints the following information:
^ C [Thread 0x682ff410 (LWP 535) exited]
[Thread 0x68aff410 (LWP 534) exited]
[Thread 0x692ff410 (LWP 533) exited]
[Thread 0x69aff410 (LWP 532) exited]
[Thread 0x6a2ff410 (LWP 531) exited]
[Thread 0x6aaff410 (LWP 530) exited]
[Thread 0x6b2ff410 (LWP 529) exited]
[Thread 0x6baff410 (LWP 528) exited]
[Thread 0x6c2ff410 (LWP 527) exited]
[Thread 0x6caff410 (LWP 526) exited]
[Thread 0x6d2ff410 (LWP 525) exited]
[Thread 0x6daff410 (LWP 524) exited]
[Thread 0x6e2ff410 (LWP 523) exited]
[Thread 0x6ecff410 (LWP 522) exited]
[Thread 0x6f647410 (LWP 521) exited]
[Thread 0x6fe47410 (LWP 520) exited]
[Thread 0x73309410 (LWP 519) exited]
[Thread 0x75718000 (LWP 516) exited]

Re: IMX7D gdb cannot debug application

igorpadykov — Mon, 23 Dec 2019 05:30:28 GMT

Hi 其东刘

for i.MX7D debug configurations may be useful to check below link

https://community.nxp.com/thread/434323?commentID=830709#comment

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

i.MX ProcessorsのトピックIMX7D gdb cannot debug application

IMX7D gdb cannot debug application

Re: IMX7D gdb cannot debug application