How do I load symbols from a shared libary?

[Aster89]

I originally asked the question on stackoverflow, but it hasn't received much attention, hence I'm asking here.

I'm debugging the C++ backend of a GUI application which lazily loads dynamic libraries (I mean .so files, at least on Linux), so what I normally do is

1. run the desktop GUI application, and take note of the PID
2. in the GUI, run whatever I need to trigger the loading of the .so files, most likely the same action for which I want to debug the C++ back-end
3. start the debugging session by attaching the debugger to that PID
4. pause
5. load the symbols for that library
6. put breakpoints where needed
7. continute
8. in the GUI, run whatever I want to debug, most likely the same thing as step 2

((Not important, really) Where step 6 can actually be done anytime, and steps 2 and 3 can be performed in reverse order too.)

If I have "adapter": "vscode-cpptools" in my JSON configuration file. Step 5 consists in running -exec shared some_library in the console (some_library has no /s and no .so extension).

But what if I want to use "adapter": "CodeLLDB"?

I've tried writing help in the console, but I don't see any reference to library, or .so, or similar.

[vadimcn]

Most of the time LLDB should be loading symbols automatically. There's target symbols add command, however, for when debug info cannot be located inside or relative to the module being loaded.

I've tried writing help in the console, but I don't see any reference to library, or .so, or similar.

Try apropos <keyword>.

[Aster89]

Thanks for the apropos tip, it'll certainly be useful.

Regarding target symbols add, entering target symbols add some_libary, where some_libary has no / in it (which is ok when using vscode-cpptools), results in error: invalid module path 'some_library'.

So I tried target symbols add /path/to/some_library.so, which resulted in a symbol file '/path/to/some_library.so' has been added to '/path/to/some_library.so', which is not an error, but a breakpoint which I put in the code that was pending, stays pending, which tells me the symbols haven't been read.

What am I doing wrong?

[vadimcn]

Assuming you are on Linux, the .so file should contain the debug symbols too, in which case lldb should just find them automatically as soon as your process loads the library. I would check whether the symbols are really there. Please see these instructions.

[Aster89]

I would check whether the symbols are really there.

I've not explicitly mentioned that with "adapter": "vscode-cpptools" the workflow I described is successful, but that's what I meant, so the symbols are there indeed.