trouble using gdb on Linux

by Zhihui Zhan » Sat, 10 May 2003 07:13:32

Hi,

I am using remote gdb to trace Linux kernel function calls. However,
whenever I type "continue" to let the user program go ahead, it fails with
"Trace/breakpoint trap",which means ther user program cannot finish
normally after being stopped inside the kernel breakpoint. Is there any
way to overcome this?

Thanks a lot,

-Zhihui

Top

1. Trouble with gdb&Linux using transitive linked shared libraries

Hello Everybody,

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
Linux.
But still, I am facing a lot of troubles in Debugging this kind of
application,
since (ddd/)gdb does wierd things with dynamic loading of those
libraries.

A) gdb opens only locally (cwd) available libraries - ignoring
LD_LIBRARY_PATH

B) (The most serios problem) On running "A", gdb complains about
unresolved symbols of libB.so, which are defined in libC.so, which are
available by
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,

Guenter

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