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

List:       koffice
Subject:    Re: compile problem koffice HEAD with KDE_3_1_BRANCH
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2003-10-21 16:39:07
[Download RAW message or body]

Well, unfortunately it looks like KOffice 1.3 will be released with bugs, as 
delaying the release even more will not bring anything either.

The wish is to try to make a last effort to remove some of the bigger bugs, 
especially in KSpread whose main developers have not had any time for months.

So for the debuggers: GDB needs more or less only to be installed and KDE will 
use it for a backtrace if something crashes.

As for Valgrind, I do not know, as I have never used it. (I have a slow 
computer, so anything as complex as Valgrind cannot be used easily.)

If you have time (or computer power) and much harddisk space and may be also 
much RAM, you can compile with --enable-debug=on (at configure time.) That 
gives extra information in the backtrace.

In the case of this bug in the file dialog, you would need to have Qt compiled 
with -debug, kdelibs and koffice with --enable-debug to have more data.

As finding bugs in Qt is not a pleasant task, you might also look at some 
other bugs, like those of KSpread. (As the address would be too long for an 
email, I cannot give it here directly. So go to the weekly summary: 
http://bugs.kde.org/weekly-bug-summary.cgi , find the line of KSpread and 
click on the number of its bug (currently:72.))

Have a nice day!

On Tuesday 21 October 2003 16:18, Giovanni Venturi wrote:
> Alle 15:55, marted́ 21 ottobre 2003, Nicolas Goutte ha scritto:
> > Bug 63946 is with Qt 3.1.2, so it is not linked to Qt 3.2 alone. :-(
> >
> > So I correct what I have written by writing now: KOffice CVS Head on KDE
> > 3.1.x is currently *not working* due to a bug.
> >
> > As for how/why it is linked to Qt, we do not know exactly yet. Clarence
> > Dang has first clues but he has not written yet that he would have found
> > more detailed information or even a fix.
> >
> > As for Trolltech, sure, they could do it, but we must be able to tell Qt
> > Bugs a litle more than that KOffice is not running. We must be able to
> > point where the bug is in Qt (or of course sending a patch.)
> >
> > As for helping, thank you. You can still help us, there are plenty of
> > bugs listed for KOffice in KDE Bugs. Most of the bugs do not really need
> > to be able to save.
> >
> > Have a nice day!
>
> I hope KOffice 1.3 will be released as soon as without bugs. How many
> problems to do Open Source Software! But it's a conquest when all is well
> done. Can you indicate me a link where to find some how-to about using of
> debugger tool David told me in the last email? valgrind, gdb, ...?
> I'd like to help Kexi, I could give help writing MySQL driver appending
> some function to the already exisisting one after the Developers ok
> obviously, because I studied MySQL C API like I sayed to Lucjian, but the
> Kexi Developers are re-writing KexiDB API, and so in the meantime I can try
> to solve some other bug into KOffice, just trying. I never do it first. I'm
> studying Qt 3.2.1 sometimes in the evening. Suggest are welcome.
> Gianni

____________________________________
koffice mailing list
koffice@mail.kde.org
To unsubscribe please visit:
http://mail.kde.org/mailman/listinfo/koffice

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