[Qt-interest] Qt 4.5.0 not 'valgrind proof'

[Christoph Duelli]

wim.delvaux at adaptiveplanet.com wrote:

> I get segfault errors in valgrind even before my app starts.
> 
> Here as sample backtrace
> 
> ==25795== Process terminating with default action of signal 11 (SIGSEGV):
> dumping core
> ==25795==  Access not within mapped region at address 0x9D
> ==25795==    at 0x6A027BD: QString::fromLocal8Bit(char const*, int)
> (qstring.cpp:3652)
> ==25795==    by 0x6AB2032: QCoreApplication::arguments()
> (qcoreapplication.cpp:1921)

Guessing without code is probably not too helpful, but still:
I once made the trivial mistake of forgetting the "&" (in int &argc) in my
QApplication-subclass's constructor. This had "interesting" effects...
Just an idea...