wine users - Aug 2009 - Help getting our application working

Hi there,

I'm one of the developers of Hero Lab ( http://www.wolflair.com/hero_lab ),
and I'm trying to investigate a problem that our users are having running
Hero Lab under WINE.

The user says he receives the following messages before Hero Lab hangs or
crashes:

> ~/.wine/drive_c/HeroLab$ wine HeroLab.exe
> fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT
(30000): STUB
> fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 30000
> fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT
(30000): STUB
> fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 30000
> fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT
(30000): STUB
> fixme:wininet:HTTPREQ_QueryOption Semi-STUB INTERNET_OPTION_SECURITY_FLAGS:
0
> fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_SECURITY_FLAGS;
STUB
> fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT
(30000): STUB
> fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 30000
> fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT
(30000): STUB
> fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 30000
> fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT
(30000): STUB
> fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT
(30000): STUB
> fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 30000
> fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT
(30000): STUB
> fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 30000
> fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT
(30000): STUB
> fixme:bitmap:CreateBitmapIndirect planes = 0
> fixme:bitmap:CreateBitmapIndirect planes = 0
> fixme:bitmap:CreateBitmapIndirect planes = 0
> fixme:bitmap:CreateBitmapIndirect planes = 0
> fixme:bitmap:CreateBitmapIndirect planes = 0
> fixme:bitmap:CreateBitmapIndirect planes = 0
> fixme:bitmap:CreateBitmapIndirect planes = 0
> fixme:bitmap:CreateBitmapIndirect planes = 0
> fixme:bitmap:CreateBitmapIndirect planes = 0
> fixme:bitmap:CreateBitmapIndirect planes = 0
> fixme:bitmap:CreateBitmapIndirect planes = 0


We only call CreateBitmapIndirect in one place in our code, which shouldn't
be being called here. What exactly is the issue that WINE is reporting, and how
do I find out where it's being called and how to fix it?

Also, he supplied the following winedbg output:

> This GDB was configured as "x86_64-linux-gnu".
> (no debugging symbols found)
> 00000008:00000019: create thread D @(nil)
> 00000008:0000001c: create thread D @(nil)
> 0008:0009: loads DLL C:\HeroLab\LFBMP13N.DLL @0x1feb0000 (0<0>)
> 0008:0009: loads DLL C:\HeroLab\LFCMP13N.DLL @0x1fcb0000 (0<0>)
> 0008:0009: loads DLL C:\windows\system32\localspl.dll @0x7e2c0000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\spoolss.dll @0x7e2b0000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\ole32.dll @0x7e390000 (0<0>)
> 0008:0009: loads DLL C:\windows\system32\rpcrt4.dll @0x7e310000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\uxtheme.dll @0x7e490000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\winex11.drv @0x7e680000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\imm32.dll @0x7e4f0000 (0<0>)
> 0008:0009: loads DLL C:\windows\system32\wininet.dll @0x7e840000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\mpr.dll @0x7e800000 (0<0>)
> 0008:0009: loads DLL C:\windows\system32\comdlg32.dll @0x7e890000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\winspool.drv @0x7e950000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\shell32.dll @0x7ea50000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\comctl32.dll @0x7e980000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\shlwapi.dll @0x7ebe0000
(0<0>)
> 0008:0009: loads DLL C:\HeroLab\LTDIS13N.dll @0x1ff70000 (0<0>)
> 0008:0009: loads DLL C:\HeroLab\ltfil13n.DLL @0x1ffc0000 (0<0>)
> 0008:0009: loads DLL C:\HeroLab\LTKRN13N.dll @0x1fff0000 (0<0>)
> 0008:0009: loads DLL C:\windows\system32\user32.dll @0x7ed40000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\gdi32.dll @0x7ec90000 (0<0>)
> 0008:0009: loads DLL C:\windows\system32\advapi32.dll @0x7ec40000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\KERNEL32.dll @0x7b820000
(0<0>)
> 0008:0009: loads DLL C:\windows\system32\ntdll.dll @0x7bc10000 (0<0>)
> 00000008:00000009: exception code=0x80000003
> warning: Target reported unsupported offsets:
Text=7bc6ba41;Data=00000005;Bss=0032fd64
> [New Thread 9]

Hopefully this will be helpful to you, because I have no idea what it means. ;)

Thanks for your help.[/quote]

Another problem I'm running into is that one of our other applications, Army
Builder, will run for a while, and then suddenly lock up with this error:

err:region:CombineRgn Invalid rgn=(nil)
err:region:CombineRgn Invalid rgn=(nil)
err:region:CombineRgn Invalid rgn=(nil)
err:region:CombineRgn Invalid rgn=(nil)

We're not calling CombineRgn anywhere in our code. How can I work out what
the problem is here?