To follow André and Yves: - If you debug code within signal/slots or event mechanisms for instance, it's very handy to trace through Qt code. In Qt, your code is often called by Qt's classes. - It also activates many Q_ASSERT checks, for instance with out-of-bounds indices. With release qt libs, this will just crash, with debug libs, it will break nicely within Qt's code... - And is there simply a good reason not to use debug libraries when debugging ?
Cheers, Etienne 2014/1/22 Yves Bailly <yves.bai...@sescoi.fr> > Le 21/01/2014 18:48, Constantin Makshin a écrit : > > There's no real need to use debug version of Qt if you don't want to > debug Qt itself, so in most > > cases the programmer won't see that warning. > > Sorry, but I strongly disagree with that... sometimes when facing a bug or > some strange, hard-to-track behaviour, it's quite handy to follow the path > of the data *inside* Qt itself. > > It's not debugging Qt, it's just trying to figure out why something is not > used or interpreted as (maybe naively) expected. > > -- > /- Yves Bailly - Software developer -\ > \- Sescoi R&D - http://www.sescoi.fr -/ > "The possible is done. The impossible is being done. For miracles, > thanks to allow a little delay." > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest