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

List:       koffice-devel
Subject:    Re: kpresenter 1.2.1 and Kpresenter 1.3
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2003-11-28 8:31:10
[Download RAW message or body]

On Thursday 27 November 2003 22:48, Giovanni Venturi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Alle 16:06, mercoledì 26 novembre 2003, Nicolas Goutte ha scritto:
> > Has the file name any hyphen (-) in it?
> >
> > Try to save with a boring simple file name. The problem is that the file
> > dialog crash seems to happen for other border cases too, where the
> > workaround cannot fix anything.
> >
> > Have a nice day!
>
> Well I recompiled KOffice with debug option and I produced a valgrind
> report using:
> valgrind kpresenter
> But a strage thing happened. Without valgring KPresenter crashed like
> reported into the the file kpresente-crash. Using valgrind "save as..."
> worked without crashing like reported into thge file "report". Why? I did
> not understand. I'm sorry but I don't remember if compiled KDE 3.1.4 with
> debug option or not. Surely not compiled Qt 3.2.1 I use with debug option
> because I didn't know that qt could be compiled with a debug option when 2
> or 3 month ago I compiled them.
> Let me know if my valgrind report if usefull or not. If I had to specify
> some option to valgrind tell me so I repeat the test. If I have to know
> something else... Why with valgrind kpresenter didn't crashed? How can it
> be? Thank you all of you,
> Gianni

The file dialog crash is a completion problem. (That is why it does not happen 
with KDE 3.2, as the completion of the file dialog was changed.)

It seems that the file dialog crash might depend on the file names shown in 
the directory, it might work for one application because there is no 
problematic file name, but not with the other because they would be a 
problematic file name. However personally, I would still like to understand 
how we have arrived at such a situation and why only KOffice seems to suffer 
if the problem is triggered in Qt 3.2 due how KDE 3.1.4 works. :-(

As for why Valgrind would not crash the application, well, I do not know. I 
just remember that when something like that happened in Windows environment, 
it meant that a variable was not correctly initialized. (In debug mode, the 
variables were nulled, in release mode, they were not. I do not know if 
Valgrind does something similar for its purposes.)

Have a nice day!

> - --
> A KDE's Italian translator
> I work on "GNU/Linux 2.4.19-4GB -- SuSE Linux 8.1"
> and "GNU/Linux 2.4.22 -- Slackware 9.0"
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQE/xnE1nT2ev4/bQKARAmSyAJ9LufS2uQ3g2JO8pBc9nDyyOFZFMQCggKkX
> pZ7s3MbNyqXXZU+Gwk3ER4A=
> =JGqM
> -----END PGP SIGNATURE-----

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

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