[Bug 83445] New: GDB does not work

Scott Shandler shandles at mail.med.upenn.edu
Wed Jun 16 14:29:27 UTC 2004

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
           Summary: GDB does not work
           Product: kdevelop
           Version: 3.0.3
          Platform: RedHat RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-devel kdevelop org
        ReportedBy: shandles mail med upenn edu

Version:           3.0.3 (using KDE KDE 3.2.2)
Installed from:    RedHat RPMs
Compiler:          gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7) 
OS:                Linux

When attempting to debug my application running on Fedora Core 2, the debugger looks for shared libraries and then dies, prior to acutually debugging the project.  See transcript:

/bin/sh -c /home/shandles/projects/tiger/libtool /usr/bin/gdb /home/shandles/projects/tiger/tiger/tiger -fullname -nx -quiet
(gdb) set edit off 
(gdb) set confirm off 
(no debugging symbols found)...
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) set print static-members on 
(gdb) tty /dev/pts/57 
(gdb) set width 0 
(gdb) set height 0 
(gdb) set stop-on 1 
(gdb) handle SIG32 pass nostop noprint 
(gdb) handle SIG43 pass nostop noprint 
(gdb) set print asm-demangle on 
(gdb) cd /home/shandles/projects/tiger/tiger 
(gdb) set args /home/shandles/projects/tiger/tiger/input/gb.in 
(gdb) break main.cpp:44 
No symbol table is loaded.  Use the "file" command.

(gdb) run 
Error while mapping shared library sections:
: Success.

(gdb) backtrace 
Error while reading shared library symbols:
: No such file or directory.

Stopped due to shared library event
#0  0x0044a480 in _dl_debug_state () from /lib/ld-linux.so.2
#1  0x0043f961 in dl_main () from /lib/ld-linux.so.2
#2  0x0044ce14 in _dl_sysdep_start () from /lib/ld-linux.so.2
#3  0x0043eac0 in _dl_start () from /lib/ld-linux.so.2
#4  0x0043e7c7 in _start () from /lib/ld-linux.so.2
(gdb) frame 0 
#0  0x0044a480 in _dl_debug_state () from /lib/ld-linux.so.2

This appears to be a problem with the way that kdevelop interacts with gdb.  I ahve tried to run the same thing outside of KDevelop and if you skip the tty line ((gdb) tty /dev/pts/57 ), it seems to work fine.  Otherwise it fails as shown above.  If there is a way to control how kdevelop interacts with GDB that would be a nice thing to let us developers do.  

In addition, the project options window is rather confusing to use.  A better organized way to set the project options, separate from the nice bells and whistles would be good too.

Thanks for the mostly excellent work!


More information about the KDevelop-devel mailing list