diff options
| author | Miikka Heikkinen <miikka.heikkinen@digia.com> | 2009-08-11 12:42:43 +0300 |
|---|---|---|
| committer | Miikka Heikkinen <miikka.heikkinen@digia.com> | 2009-08-11 12:42:43 +0300 |
| commit | f79228b71b05d28b83014f262bc47e3fe9557a14 (patch) | |
| tree | 3c6bff18774b9294ea1eeef7cc69186c078dd504 /tests/auto/qtextlayout | |
| parent | 70e098d965318651acb725374b73e026f2946b76 (diff) | |
RVCT didn't like a test bool variable exported directly from QtGui,
causing applications to panic with KERN-EXEC 3. Fixed by providing
accessor for the bool in question instead of exporting it directly.
Note: Unknown why exactly this panic occurs, as exporting bools works
just fine when tested with small test executable + dll. Something
in QtGui causes this to fail; I suspect it might be the massive
code segment size and relocation of the data segment that is
contributing to this problem.
RevBy: Jason Barron
Diffstat (limited to 'tests/auto/qtextlayout')
| -rw-r--r-- | tests/auto/qtextlayout/tst_qtextlayout.cpp | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/tests/auto/qtextlayout/tst_qtextlayout.cpp b/tests/auto/qtextlayout/tst_qtextlayout.cpp index e948cf2023..d76f3871e1 100644 --- a/tests/auto/qtextlayout/tst_qtextlayout.cpp +++ b/tests/auto/qtextlayout/tst_qtextlayout.cpp @@ -57,8 +57,6 @@ #define TESTFONT_SIZE 12 - - //TESTED_CLASS= //TESTED_FILES= @@ -164,12 +162,12 @@ void tst_QTextLayout::getSetCheck() } QT_BEGIN_NAMESPACE -extern Q_GUI_EXPORT bool qt_enable_test_font; +extern void qt_setQtEnableTestFont(bool value); QT_END_NAMESPACE tst_QTextLayout::tst_QTextLayout() { - qt_enable_test_font = true; + qt_setQtEnableTestFont(true); } tst_QTextLayout::~tst_QTextLayout() |