1. Trouble with gdb&Linux using transitive linked shared libraries
currently I am porting a huge Softwareproject to Linux, where we
excessively used shared libraries ( *.so ), and of course all the
kinds of transitive/
recursive dependencies in the software project.
That means executable A links against libB.so, which itself is linked
against libC.so and libD.so, they are again.... and so on.
After some trouble with ld, (-rpath <directory> additional to
-L<directory> as on other Unix systems), we finally got it running on
But still, I am facing a lot of troubles in Debugging this kind of
since (ddd/)gdb does wierd things with dynamic loading of those
A) gdb opens only locally (cwd) available libraries - ignoring
B) (The most serios problem) On running "A", gdb complains about
unresolved symbols of libB.so, which are defined in libC.so, which are
proper runtime linking - and are running without gdb.
Who has some answers - faced the same problems - solutions etc. ?
I cannot develop software without having a proper debugger.
Currently we are using gcc 2.95.3 / gdb 5.0
Thanks in advance,
2. some clients don't work connecting to proftd
3. Using GDB to debug a program that uses fork(2)?
4. Networking Problems
5. using gdb on linux
6. Connect Script failed
7. debugging a shared library using gdb on linux
8. buffer_head size
9. Using gdb with Linux Elf shared object libraries
10. gdb/xxgdb terminal trouble
11. GDB Trouble
12. trouble with linux14, gcc, gdb..
13. help! gdb trouble