[Bug 31157] Filemaker Pro 12 Trial crashes when opening a sample solution

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Jul 20 14:28:36 CDT 2014


https://bugs.winehq.org/show_bug.cgi?id=31157

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download
             Status|UNCONFIRMED                 |NEW
                URL|                            |http://download.cnet.com/Fi
                   |                            |leMaker-Pro/3000-2065_4-107
                   |                            |20179.html
                 CC|                            |focht at gmx.net
            Summary|Filemaker Pro 12 Trial      |Filemaker Pro 12 Trial
                   |crashes                     |crashes when opening a
                   |                            |sample solution
     Ever confirmed|0                           |1

--- Comment #6 from Anastasius Focht <focht at gmx.net> ---
Hello folks,

confirming, still present.

--- snip ---
$ pwd
/home/focht/.wine/drive_c/Program Files/FileMaker/FileMaker Pro 12

$ WINEDEBUG=+tid,+seh,+relay wine ./FileMaker\ Pro.exe >>log.txt 2>&1
...
002d:Call imm32.ImmCreateContext() ret=00967818
...
002d:Ret  imm32.ImmCreateContext() retval=0b8f77b0 ret=00967818
002d:Call imm32.ImmAssociateContext(0004021a,0b8f77b0) ret=0096782d
002d:Call KERNEL32.IsBadReadPtr(0b8f77b0,00000150) ret=7e50a0a0
002d:Ret  KERNEL32.IsBadReadPtr() retval=00000000 ret=7e50a0a0
002d:Call user32.RemovePropW(0004021a,7e512320 L"WineImmHIMCProperty")
ret=7e50a1c3
002d:Ret  user32.RemovePropW() retval=00000000 ret=7e50a1c3
002d:Call user32.SetPropW(0004021a,7e512320 L"WineImmHIMCProperty",0b8f77b0)
ret=7e50a236
002d:Ret  user32.SetPropW() retval=00000001 ret=7e50a236
002d:Call user32.IsWindow(00000000) ret=7e50a275
002d:Ret  user32.IsWindow() retval=00000000 ret=7e50a275
002d:Call user32.IsWindow(0004021a) ret=7e50a2bb
002d:Ret  user32.IsWindow() retval=00000001 ret=7e50a2bb
002d:Call user32.SendMessageW(0004021a,00000281,00000001,c000000f) ret=7e50a2e8
002d:Call window proc 0x78a3c187
(hwnd=0x4021a,msg=WM_IME_SETCONTEXT,wp=00000001,lp=c000000f)
002d:Call KERNEL32.ActivateActCtx(00184f60,0033a570) ret=78a3ba3e
002d:Ret  KERNEL32.ActivateActCtx() retval=00000001 ret=78a3ba3e
002d:trace:seh:raise_exception code=c0000005 flags=0 addr=0x732ed6 ip=00732ed6
tid=002d
002d:trace:seh:raise_exception  info[0]=00000000
002d:trace:seh:raise_exception  info[1]=00000004
002d:trace:seh:raise_exception  eax=00000000 ebx=c000000f ecx=00000000
edx=00000000 esi=00000000 edi=0808f798
002d:trace:seh:raise_exception  ebp=0033a450 esp=0033a388 cs=0023 ds=002b
es=002b fs=0063 gs=006b flags=00010246 
...
Unhandled exception: page fault on read access to 0x00000004 in 32-bit code
(0x00732ed6).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:00732ed6 ESP:0033a388 EBP:0033a450 EFLAGS:00010246(  R- --  I  Z- -P- )
 EAX:00000000 EBX:c000000f ECX:00000000 EDX:00000000
 ESI:00000000 EDI:0808f798
...
Backtrace:
=>0 0x00732ed6 in filemaker pro (+0x332ed6) (0x0033a450)
0x00732ed6: movl    0x4(%esi),%eax
Modules:
Module    Address            Debug info    Name (277 modules)
PE      350000-  35e000    Deferred        xalanmessages_1_11
PE      360000-  3e4000    Deferred        proofreader
PE      3f0000-  3f9000    Deferred        omnithread
PE      400000- 10f4000    Export          filemaker pro
PE     1100000- 11fd000    Deferred        dli_pdfl91
PE     1200000- 1238000    Deferred        xgrfx
PE     1240000- 1431000    Deferred        support
PE     1440000- 155a000    Deferred        libeay32 
...
Threads:
process  tid      prio (all id:s are in hex)
..
0000002c (D) C:\Program Files\FileMaker\FileMaker Pro 12\FileMaker Pro.exe
    0000004d    0
    0000004c    0
    0000004b    0
    0000004a    0
...
    00000030    0
    0000002f    0
    0000002e    0
    0000002d    0 <== 
--- snip ---

@Maik

--- quote ---
Unfortunately my trial version has expired. Is there any registry key I might
remove?
--- quote ---

That's one of the reasons why you install each app in a separate WINEPREFIX.
Trial expired -> throw away the old prefix and install app in new prefix.

Another way is to use tools that allow to snapshot the whole prefix, for
example managing prefixes with btrfs subvolumes (I use the snapshot feature to
quickly transition/reset/revert to any state).

Of course there are other methods to reset the trial.
I'm sure you understand why "recipes" or description how the mechanism works
doesn't belong here (unless it's needed to fix a bug related to DRM scheme).

$ sha1sum fmp_trial_fm_12.0.1.183.exe 
feccde9dc759da0f924fd3b0498bad2c61b496da  fmp_trial_fm_12.0.1.183.exe

$ du -sh fmp_trial_fm_12.0.1.183.exe 
276M    fmp_trial_fm_12.0.1.183.exe

$ wine --version
wine-1.7.22-70-g509bdae

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list