PDA

View Full Version : QPageSetupDialog is crashing always



senthilsp
29th November 2007, 10:51
Hello All

Greetings,
I am using QT 4.3.1 commercial version in Windows XP operation system.
I have written below code snippet to invoke QPageSetupDialog in an QT windows application.

QPrinter printer( QPrinter::HighResolution );
QPageSetupDialog objPageSetup(&printer,this);
if (objPageSetup.exec() == QDialog::Accepted)
{
QMessageBox::about(NULL,"QPageSetupDialog"," QPageSetupDialog ");
}

Whenever I execute this code, I am able to see the QPageSetupDialog window.When I click the “Ok” in it, It get crashing.

Error details that I get after crashing are as follows

Call Stack details
> ntdll.dll!7c901230()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!7c96c943()
ntdll.dll!7c96cd80()
ntdll.dll!7c96df66()
uxtheme.dll!5ad74de3()
uxtheme.dll!5ad74d8d()
ntdll.dll!7c94a5d0()
user32.dll!7e41d074()
user32.dll!7e418bd9()
user32.dll!7e41885a()
user32.dll!7e41882a()
user32.dll!7e41882a()
user32.dll!7e41b4c0()
ntdll.dll!7c9268ad()
user32.dll!7e41dadf()
ntdll.dll!7c90eae3()
user32.dll!7e4186e7()
user32.dll!7e42db47()
user32.dll!7e42593f()
kernel32.dll!7c80fcff()
comdlg32.dll!763d38f5()
ntdll.dll!7c96e0d4()
ntdll.dll!7c94a5d0()
ntdll.dll!7c926abe()
ntdll.dll!7c94a1f5()
ntdll.dll!7c91b5f4()
ntdll.dll!7c91b686()
ntdll.dll!7c94a1f5()
ntdll.dll!7c91b686()
ntdll.dll!7c926abe()
ntdll.dll!7c91b686()
ntdll.dll!7c91b298()
ntdll.dll!7c9106eb()
ntdll.dll!7c91b686()
ntdll.dll!7c91b298()
ntdll.dll!7c9106eb()
ntdll.dll!7c96d8a2()
ntdll.dll!7c91056d()
ntdll.dll!7c917cb7()
ntdll.dll!7c917bb0()
ntdll.dll!7c96d886()
ntdll.dll!7c949d18()
ntdll.dll!7c96cde9()
ntdll.dll!7c91b686()
ntdll.dll!7c96d886()
ntdll.dll!7c91b686()
ntdll.dll!7c96d6cc()
ntdll.dll!7c96d886()
ntdll.dll!7c9106eb()
kernel32.dll!7c80fe6f()
kernel32.dll!7c80fe25()
comdlg32.dll!763d3ae6()
comdlg32.dll!763d4919()

Please find the attached error message box snap shot which I get after crashing.
It would be grateful if any information is shared about the same.
Thanks

wysota
29th November 2007, 11:21
The call stack is useless - you need to compile in debug mode, so that the symbol names are visible. The code snippet doesn't say much either, could you provide more code?