Qt4-preview-feedback Archive, April 2007
QT & valgrind
Message 1 in thread
Hi, I was just wondering (as I am running my app through
valgrind) why there are SO many warnings/errors in QT
stuff along the lines of:
Conditional jump or move depends on uninitialised value(s)
Im using QT 4.3 beta on linux fedora 6
Im no expert in C++, however Ive been able to find
many problems in my own code through valgrind that I would
not have seen otherwise very easily.
It would seem to me that potentially many of the bugs that
QT gets reported may be due to valgrind warnings that are yet
to be fixed.
As a secondary issue, its a *pain in the butt* adding all of
these issues to my suppression file, especially when many of
them occur in ever instance of a QGraphicsItem's and their
related methods. There are literally hundreds sometimes.
My request is simple, where possible can QT please fix these
so that I dont have to spend hours adding things to my suppression
file? It may even fix some well hidden QT bugs.
Thanks :)
Jeff
To unsubscribe - send "unsubscribe" in the subject to qt4-preview-feedback-request@xxxxxxxxxxxxx
Message 2 in thread
Hi,
> Hi, I was just wondering (as I am running my app through
> valgrind) why there are SO many warnings/errors in QT
> stuff along the lines of:
>
> Conditional jump or move depends on uninitialised value(s)
>
> Im using QT 4.3 beta on linux fedora 6
>
> Im no expert in C++, however Ive been able to find
> many problems in my own code through valgrind that I would
> not have seen otherwise very easily.
>
> It would seem to me that potentially many of the bugs that
> QT gets reported may be due to valgrind warnings that are yet
> to be fixed.
Valgrind issues have often been discussed on Qt mailing lists:
http://www.google.com/search?q=valgrind&sitesearch=lists.trolltech.com
Qt is routinely checked with Valgrind and other memory debuggers.
I think most of the "many" bugs reported in Qt are not memory errors and could
not be detected with a memory debugger such as Valgrind. An then some memory
errors were not detected because the tests run at Trolltech do not follow a
particular code path (this can still happen with 100% test coverage).
Many of the of the warnings you see could be false alarms. Some of these
warnings cannot be easily worked around. However you may write your own
suppression file:
http://valgrind.org/docs/manual/faq.html#faq.writesupp
If you think you've found real problems in Qt, please post the error messages.
--
[ signature omitted ]
