Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Solved Sandglass breakpoints, not load shared library symbols depends on *.so loading

    General and Desktop
    2
    4
    235
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      p535 last edited by

      Good day!
      I build shared library config.so, which starts from some executable by two ways (depends on where it placed, two near folder):

      1. directly dlopen... from exec;
      2. through second library.
        My library is the same.

      When I starts debugging with case 2, breakpoints have sandglasses and the output contains:

      Could not load shared library symbols for config/config.so.
      Do you need "set solib-search-path" or "set sysroot"?

      Has anyone dealt with something like this?

      Qt 5.11.0 (GCC 6.3.0 20170516, 64) Qt Creator 4.6.2

      JonB 1 Reply Last reply Reply Quote 0
      • JonB
        JonB @p535 last edited by

        @p535 said in Sandglass breakpoints, not load shared library symbols depends on *.so loading:

        solib-search-path

        No, but why don't you just Google this and set it to point to the necessary directory? E.g. https://stackoverflow.com/questions/44896217/how-to-save-set-solib-search-path shows its usage and how to save for future?

        P 1 Reply Last reply Reply Quote 0
        • P
          p535 @JonB last edited by

          @JonB thank you!
          When I place .gdbinit with "set solib-search-path /dir-with-so/" in home directory, the breakpoints began to work.
          *seems like not a proper way?

          JonB 1 Reply Last reply Reply Quote 0
          • JonB
            JonB @p535 last edited by

            @p535
            Good. Don't know what you mean by "seems like not a proper way". If you have to tell gdb where they are so it knows, that seems OK.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post