Code::Blocks Forums
User forums => Embedded development => Topic started by: Kaijun on December 20, 2011, 12:27:53 pm
-
I use C::B as debugger with gdbserver. I found I can display a source file by double clicking a file on call stack window for some shared libs. but not for other shared libs. I can not figure out, I am not sure if this issue is related to C::B or to libs build options. Any idea?
-
Are there any paths to the sources of the shared lib in the call stack window?
Do you have debug info for the libs in question?
What OS are you using?
-
I also wonder why there are no full paths to the source files of shared libs in question.
All shared libs are built to debug version with openembedded linux.
-
I use C::B as debugger with gdbserver. I found I can display a source file by double clicking a file on call stack window for some shared libs. but not for other shared libs. I can not figure out, I am not sure if this issue is related to C::B or to libs build options. Any idea?
1, the first thing is that you can show us the debugger's debug log message.
2, I guess the issue is related this GDB post: http://sourceware.org/ml/gdb-patches/2011-12/msg00100.html
You can see it has a new patch to handle this correctly.
Currently gdb will show the file path you pass to GCC when you compile the shared library. With the patch above, you have many options, the default option is show "full path of the source file".