[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice
Subject:    Re: How do I debug KWord?
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-05-31 19:16:30
[Download RAW message or body]

On Wed, May 31, 2000 at 08:10:30PM +0100, Shaheed Haque wrote:
> I'm having great trouble debugging (the floating frame support I'm adding to 
> KWord) because gdb seems completely incapable of correctly doing symbolic 
> debug. For example, the "bt" command gives complete nonsense for both 
> function name and filename/linenumber.
> 
> I've tried:
> 
> - upgrading gdb (to 4.18-12)

Try 5.0.
I'm using gdb from CVS, but I think 5.0 has been released too, a few days ago.

There's a gui with it (huh, slow), but gdb -nw works fine.

> - checking LD_LIBRARY_PATH and /etc/ld.so.conf for any stale copies of 
> libraries
> 
> - checking that the image and library contain symbols:
> 
> $ file `which kword`
> /opt/kde2/bin/kword: ELF 32-bit LSB executable, Intel 80386, version 1, 
> dynamically linked (uses shared libs), not stripped
> $ file /opt/kde2/lib/libkword.so
> /opt/kde2/lib/libkword.so: ELF 32-bit LSB shared object, Intel 80386, 
> version 1, not stripped

Also make sure kdelibs is compiled with --enable-debug.

Finally, make sure you export KDE_DEBUG=1 to avoid the crash handler, or start
apps with --nocrashhandler.

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today
See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2

[prev in list] [next in list] [prev in thread] [next in thread]