Remote Debugging: Unable to find dynamic linker breakpoint function

Situation:

Using QT Creater, trying to debug a program on remote device.  I set the breakpoints on the IDE but the breakpoints are not active and program does not stop.

Action:

The “Unable to find dynamic linker breakpoint” seemed pretty suspioucous so looked into that. Realized that I did not have the environment variable sysroot set to a copy of the target filesystem.

Within QT Creator you can set an environment variable in the Projects->Run Settings->Run->System Environment

variable: sysroot

value: /path/to/targetfs

Result:

While I still see the Unable to find dynamic linker breakpoint message, the program now stops at breakpoints I set on the IDE.  Semi resolved.

 

Resources:

Below link is really good at explaining the issue.

http://www.fayewilliams.com/2013/01/31/gdb-unable-to-find-dynamic-linker-breakpoint-function/

http://e2e.ti.com/support/embedded/linux/f/354/t/102838.aspx

Advertisements
This entry was posted in troubleshooting and tagged , , , . Bookmark the permalink.

3 Responses to Remote Debugging: Unable to find dynamic linker breakpoint function

  1. Lorenzo says:

    Hi, I’m facing a similar problem: I wrote a plugin and I want to use it in a project. However, when I set a breakpoint in the plugin code, the debug on device doesn’t stop (whereas the debug on desktop does)… could you please explain a bit more extensively the way you set sysroot in qtcreator? Because I don’t see Run->System Environment QTC 3.4… Thank you so much!

  2. Lorenzo says:

    Thanks! I solved by making a symbolic link to the libraries into the directory targeted by set solib-search-path. Cheers

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s