forked from qt-creator/qt-creator
The location of the dll doesn't depend on the application's current directory but its binary's location. This caused the manual test to turn false positive when running from Creator, because on Windows, the binaries are placed in a subdirectory named "debug" or "release", respectively. Change-Id: Ie5115fbacd30ad0ef85bc258d405ae3ac42f8ece Reviewed-by: hjk <hjk@qt.io>
Thinks to check: - loading of custom dumpers (as seen on QByteArray/QString) - availability of Qt debug information (custom display of QObject derived class) - availabitily of Qt sources (single step into some Qt *._cpp_ file) - setting of breakpoints on dynamically loaded plugins (try plugin.cpp here, especially in constructors) - check I/O (qDebug, std::cout, std::cerr)