Hi Andrey -

Sorry it's taken a few days to get around to this, but very willing to provide further assistance as required.

Mini dump attached and stack trace below, both from v3.33

Regards - Philip


wow64win.dll+0x3fe3a
wow64win.dll+0x1aea8
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x2d
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64KiUserCallbackDispatcher+0x204
wow64win.dll+0x34583
ntdll.dll!KiUserCallbackDispatcher+0x1f
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x676
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x42b
ntdll.dll!RtlUniform+0x6e6
ntdll.dll!RtlCreateTagHeap+0xa7
ntdll.dll!LdrInitializeThunk+0xe
USER32.dll!DispatchMessageW+0x5c
pwsafe.exe!AfxInternalPumpMessage+0x18
pwsafe.exe!CGeneralMsgBox::MessageBoxW+0x1fd
pwsafe.exe!DboxMain::ChangeMode+0x4e3
pwsafe.exe!DboxMain::LockDataBase+0x160
pwsafe.exe!DboxMain::OnSize+0x340
pwsafe.exe!CWnd::OnWndMsg+0x501
pwsafe.exe!CWnd::WindowProc+0x22
pwsafe.exe!DboxMain::WindowProc+0x2ee
pwsafe.exe!AfxCallWndProc+0xb0
pwsafe.exe!AfxWndProc+0x34
USER32.dll!gapfnScSendMessage+0x332
USER32.dll!GetThreadDesktop+0xd7
USER32.dll!GetClientRect+0xc5
USER32.dll!CallWindowProcW+0x1b
pwsafe.exe!CSubclassWnd::WindowProc+0x27
pwsafe.exe!CCoolMenuManager::WindowProc+0x5a
pwsafe.exe!CMenuTipManager::WindowProc+0x80
pwsafe.exe!HookWndProc+0xa1
USER32.dll!gapfnScSendMessage+0x332
USER32.dll!GetThreadDesktop+0xd7
USER32.dll!LoadStringW+0x210
USER32.dll!gapfnScSendMessage+0xac4
USER32.dll!GetPropW+0x73
USER32.dll!gapfnScSendMessage+0xbfc
USER32.dll!GetCursor+0x3c5
USER32.dll!GetCursor+0x1a9
USER32.dll!gapfnScSendMessage+0x332
USER32.dll!GetThreadDesktop+0xd7
USER32.dll!GetClientRect+0xc5
USER32.dll!CallWindowProcW+0x1b
pwsafe.exe!CWnd::DefWindowProcW+0x46
pwsafe.exe!CWnd::WindowProc+0x39
pwsafe.exe!DboxMain::WindowProc+0x2ee
pwsafe.exe!AfxCallWndProc+0xb0
pwsafe.exe!AfxWndProc+0x34
USER32.dll!gapfnScSendMessage+0x332
USER32.dll!GetThreadDesktop+0xd7
USER32.dll!GetClientRect+0xc5
USER32.dll!CallWindowProcW+0x1b
pwsafe.exe!CSubclassWnd::WindowProc+0x27
pwsafe.exe!CCoolMenuManager::WindowProc+0x5a
pwsafe.exe!CMenuTipManager::WindowProc+0x80
pwsafe.exe!HookWndProc+0xa1
USER32.dll!gapfnScSendMessage+0x332
USER32.dll!GetDC+0x52
USER32.dll!GetThreadDesktop+0x185
USER32.dll!LoadStringW+0xee
ntdll.dll!KiUserCallbackDispatcher+0x2e
pwsafe.exe!DboxMain::OnMinimize+0x33
pwsafe.exe!_AfxDispatchCmdMsg+0x42
pwsafe.exe!CCmdTarget::OnCmdMsg+0x120
pwsafe.exe!CPropertySheet::OnCmdMsg+0x1b
pwsafe.exe!CWnd::OnCommand+0x89
pwsafe.exe!CWnd::OnWndMsg+0x3c
pwsafe.exe!CWnd::WindowProc+0x22
pwsafe.exe!DboxMain::WindowProc+0x2ee
pwsafe.exe!AfxCallWndProc+0xb0
pwsafe.exe!AfxWndProc+0x34
USER32.dll!gapfnScSendMessage+0x332
USER32.dll!GetThreadDesktop+0xd7
USER32.dll!GetClientRect+0xc5
USER32.dll!CallWindowProcW+0x1b
pwsafe.exe!CSubclassWnd::WindowProc+0x27
pwsafe.exe!CCoolMenuManager::WindowProc+0x5a
pwsafe.exe!CMenuTipManager::WindowProc+0x80
pwsafe.exe!HookWndProc+0xa1
USER32.dll!gapfnScSendMessage+0x332
USER32.dll!GetThreadDesktop+0xd7
USER32.dll!CharPrevW+0x138
USER32.dll!DispatchMessageW+0xf
pwsafe.exe!AfxInternalPumpMessage+0x3e
pwsafe.exe!CWnd::RunModalLoop+0xc3
pwsafe.exe!CWnd::CreateRunDlgIndirect+0x3e
pwsafe.exe!CDialog::DoModal+0x10a
pwsafe.exe!ThisMfcApp::InitInstance+0x46e
pwsafe.exe!CWinApp::InitApplication+0x3b
pwsafe.exe!AfxWinMain+0x46
ntdll.dll!RtlInitializeExceptionChain+0x63
ntdll.dll!RtlInitializeExceptionChain+0x36



On 1 April 2014 06:01, Andrey Kuznetsov <pm_kan@users.sf.net> wrote:

This week I've tried once more to reproduce the bug in Win8.1 Pro x64, but without luck. Can someone, who have the issue create and attach pwsafe.cfg and minidump or call stack when message box with error is displayed. Because at this time database isn't opened and password wasn't entered yet, it will not reveal data from container (you can create empty database and run it from account of temporary user).

Unfortunatelly standard task manager can't create correct dump for 32-bit app on 64-bit OS. So it's better to use Process Explorer (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx)

To create full or minidump with Process Explorer: find pwsafe process in the list, right click on it, then select Create Dump-> Create Mini Dump

To get a call stack with Process Explorer:
- download PDB files for pwsafe 3.33 (you can find them in files section: pwsafe-3.33-map+pdb.zip)
- unpack them somewhere and put path to "releasem" subdirectory to Process Explorer's symbols settings (Options->Configure Symbols:Symbols path)
- double click on pwsafe process and select "Threads" tab
- on each list item that have "pwsafe.exe" in "Start address" column click "Stack" button (or just double click on list item) and copy all data.


[bugs:#1149] "Requested mode change failed"

Status: accepted
Group: v1.0_(example)


Created: Sun Dec 08, 2013 08:07 PM UTC by Philip Le Riche
Last Updated: Mon Feb 24, 2014 12:25 AM UTC
Owner: Rony Shapiro

Having upgraded to v3.32, launching PaswordSafe (with -s option) gives a popup with a title "Requested mode change failed", saying "Failed to switch from R/W to R-O: Could not release database lock." Clicking OK, PasswordSafe appears to run normally.


Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/passwordsafe/bugs/1149/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/