-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to specify the path to source code of shared labrary ? #375
Comments
... have you checked how this works in GDB? Using my favorite search machine the third entry is https://sourceware.org/gdb/onlinedocs/gdb/Source-Path.html which explains "it doesn't matter as long as you have the cwd within gdb set identical to the cwd during compile time or compile with full paths" and also mentions the For this extension it would be the settings ... and of course the shared library has the have been compiled and linked with debug info ( |
Thank you !! ~/test/test.c mylib.so test and I run gdb with test.o that calls mylib.so target: "./test" with just gdb I can make a break point in mylib.c with : b funtion_name thank you! |
You give the "main source code path" via For specifying multiple directories: "autorun": [
"directory ~/dev/mylib",
"directory ~/test"
], |
Thank you !! it works :) |
@WebFreak001 @brownts: Do you think an array setting |
Is this a case where full source paths are not being used during the compilation of the shared library? I would think this should work as-is without needing additional paths specified unless full paths are not being used. Additionally, it might be necessary to allow pending breakpoints so that the breakpoint is set in the shared library once it is loaded. I'm not sure I fully understand the cause of this issue. |
Hi,
is there a way to specify the path to the source code of a library (.so) file ?
I would like to put breakpoints in my library, and see how it runs, the source code is in a different directory than the executable with which I run gdb.
If it's possible would you please show an example.
Thank you!
The text was updated successfully, but these errors were encountered: