http://bugs.winehq.org/show_bug.cgi?id=12099
Summary: .NET Framework 1.1 installer requires loadperf.dll in
case of AeDebug -> Auto=0 (unhandled exception dialog)
Product: Wine
Version: CVS/GIT
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Created an attachment (id=11486)
--> (http://bugs.winehq.org/attachment.cgi?id=11486)
example patch to add loadperf.dll and simple UnloadPerfCounterTextStringsW stub
preventing .NET 1.1 installer exception
Hello,
VS.NET 7.x installers modify AeDebug which results in error message box from
.NET Framework 1.1 installer due to an unhandled exception.
With default AeDebug Auto=1 and standalone .NET 1.1 installation you won't
notice it because this exception doesn't affect overall "success" result of
installer.
You can capture output from console to see winedbg actually spawned.
VS.NET 7.x installers add/modify the following JIT debugging keys:
--- snip ---
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\AeDebug\Debugger
Auto: 1 -> 0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
Default: cordbg.exe !a 0x%x8
--- snip ---
Extract from .msi file:
--- snip ---
_FldbVs7eve_RegFile_887_00017.3643236F_FC70_11D3_A536_0090278A1BB8 2
SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug Auto 0
_VS_Debugging___VS7JIT_____X86.3643236F_FC70_11D3_A536_0090278A1BB8)
..
--- snip ---
You can simulate the behaviour on clean ~/.wine if you manually set
AeDebug/Auto=0 (default is 1) and then execute the standalone .NET 1.1
installer.
--- snip ---
002d:Call KERNEL32.lstrlenA(0034f55c "2008-03-17
21:20:25\t\tStarting\tUninstalling performance counters\r\n") ret=79e88b92
..
002d:Call KERNEL32.LoadLibraryA(79e61310 "loadperf.dll") ret=79e907ed
002d:Ret KERNEL32.LoadLibraryA() retval=00000000 ret=79e907ed
002d:Call KERNEL32.GetLastError() ret=79e907f9
002d:Ret KERNEL32.GetLastError() retval=0000007e ret=79e907f9
002d:Call KERNEL32.RaiseException(c06d007e,00000000,00000001,0034f960)
ret=79e9082c
002d:trace:seh:raise_exception code=c06d007e flags=0 addr=0x7b8419a0
002d:trace:seh:raise_exception info[0]=0034f910
002d:trace:seh:raise_exception eax=7b82c3e9 ebx=7b8af3e4 ecx=00000000
edx=0034f904 esi=0034f904 edi=0034f880
002d:trace:seh:raise_exception ebp=0034f868 esp=0034f804 cs=0073 ds=007b
es=007b fs=0033 gs=003b flags=00200212
002d:trace:seh:call_stack_handlers calling handler at 0x402518 code=c06d007e
flags=0
..
002d:Call KERNEL32.UnhandledExceptionFilter(0034f350) ret=7c34c456
wine: Unhandled exception 0xc06d007e at address 0x7b8419a0 (thread 002d),
starting debugger...
002d:Call user32.MessageBoxA(00000000,0034efd8 "Unhandled exception 0xc06d007e
at address 0x7b8419a0.\nDo you wish to debug it?",7b8a3e47 "Exception
raised",00000014) ret=7b841deb
--- snip ---
The message box is shown with the option to dismiss the exception or to debug
it.
This can be pretty confusing to users who have no knowledge how to deal with
this.
Well, actually this exception should never occur.
Wine can prevent this problem by providing a simple loadperf.dll and
UnloadPerfCounterTextStringsW stub.
Output after patch:
--- snip ---
0041:Ret KERNEL32.LoadLibraryA() retval=607d0000 ret=79e907ed
0041:Call KERNEL32.InterlockedExchange(79e96fa8,607d0000) ret=79e9083e
0041:Ret KERNEL32.InterlockedExchange() retval=00000000 ret=79e9083e
0041:Call KERNEL32.GetProcAddress(607d0000,79e919b4
"UnloadPerfCounterTextStringsW") ret=79e908c4
0041:Ret KERNEL32.GetProcAddress() retval=607d8808 ret=79e908c4
0041:Call loadperf.UnloadPerfCounterTextStringsW(0034f9d0 L"u
\"ASP.NET_1.1.4322\"",00000001) ret=79e86e64
0041:fixme:loadperf:UnloadPerfCounterTextStringsW (L"u \"ASP.NET_1.1.4322\"",
1): stub!
0041:Ret loadperf.UnloadPerfCounterTextStringsW() retval=00000000 ret=79e86e64
--- snip ---
Please add this dll and the UnloadPerfCounterTextStringsW stub.
The attached patch is provided as example to quickly validate the problem
solution.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=13463
Summary: 000
Product: WineHQ Bugzilla
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P5
Component: bugzilla-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: maty1206(a)maryanlinux.com
Wine can't uninstall the trial of Filemaker Pro.
Please, improve this feature.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=14844
Summary: Filemaker 9- freezes when loading .fmx plugins
Product: WineHQ Apps Database
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: appdb-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mosborne(a)ashs.school.nz
Filemaker 9 runs perfectly in Wine until it tries to load plugins, such as
Troi_*.fmx
Normally these extensions are (I think) located in the Application data folder
in windows so Wine might be looking for them in the wrong place. Ideas?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=12356
Summary: FileMaker 8.5 and 9 crash after a few second on startup
Product: Wine
Version: 0.9.58.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: winedbg
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mihael.krauth(a)gmail.com
FileMaker 8.5 and 9 crash after a few second on startup, just afer displaying
the splash screen.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=14963
Summary: Filemaker pro 8.5 apps crash easily (version 6.0 didn't)
Product: Wine
Version: 1.0.0
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: julien.puydt(a)laposte.net
Created an attachment (id=15570)
--> (http://bugs.winehq.org/attachment.cgi?id=15570)
Crash trace
A small app (named rech_pb.exe) to query a database "written" with filemaker
pro 8.5 shows empty dropdown menus, and can crash pretty easily when used ; it
shows many :
fixme:ole:OleQueryLinkFromData (0x13a448),stub!
and many :
fixme:font:SetMapperFlags (0x8258, 0x00000000): stub - harmless
An older version of the same app "written" with filemaker pro 6.0 works
correctly, but shows many :
fixme:ole:OleQueryLinkFromData (0x13a448),stub!
so I guess those warnings are pretty harmless, but the "harmless" ones aren't
that much.
See the attached log of a crash of the newer version.
Hope that helps.
PS: I'm using debian unstable's 1.0.0-1 package, in case the precision can help
PS2: I'm probably tech-savvy enough to install svn+patch if needed
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=9773
Summary: FileMaker crashes
Product: WineHQ Apps Database
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: website-bugs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hhalvors(a)princeton.edu
Created an attachment (id=8211)
--> (http://bugs.winehq.org/attachment.cgi?id=8211)
partial backtrace
Wine 0.9.39, trying to run FileMaker Pro 8.5. Installation went great.
I can start FileMaker, and I can open a database. However, when I click on the
screen, FileMaker crashes. I have attached a partial backtrace.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=15022
Summary: msi.dll.MsiDatabaseMergeW not implemented
Product: Wine
Version: 1.1.3
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: aruiz(a)gnome.org
Created an attachment (id=15664)
--> (http://bugs.winehq.org/attachment.cgi?id=15664)
Wix test case
While trying to run wix[0]'s candle tool with mono[1] I get this error:
wine: Call from 0x7ee510e0 to unimplemented function msi.dll.MsiDatabaseMergeW,
aborting
Are there any plans to support this function anytime soon?
[0] http://wix.sourceforge.net/
[1] http://www.go-mono.com/mono-downloads/download.html
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=11414
Summary: msidb:STREAMS_modify 0x1c2178 3 0x12d2aa0 - mode not
implemented
Product: Wine
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jdahlin(a)async.com.br
To be able to test this you need to install mono on win32. I used the 1.2.6
version.
I installed the latest beta of WiX, 3.0.2925 available from
wix.sourceforge.net.
First light.exe needs to be run on product.wxs on the
examples/public/first/product.wxs, this generated product.wixobj.
After that I run, with only builtin dlls:
wine ../light.exe "-cultures:en-us" product.wixobj
fixme:msidb:STREAMS_modify 0x1c2178 3 0x12d2aa0 - mode not implemented
light.exe : error LGHT0001 : Some sort of w32 error occurred: 120
Exception Type: System.ComponentModel.Win32Exception
Stack Trace:
[mono backtrace cut]
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=11411
Summary: GetFileVersionInfoSizeW returns wrong error code if file
has no version (affects WiX)
Product: Wine
Version: 0.9.54.
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Keywords: patch
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
http://blog.rvburke.com/2008/01/30/gtk-and-pygtk-on-win32/
complained about WiX not running.
http://www.winehq.org/pipermail/wine-patches/2007-November/046456.html
talks about two changes needed to get it closer to running.
It seems to have been dropped, so here's one of the two bugs
it reports:
Running light.exe from wix on a wixobj file with a non-versioned
file as a component prints a diagnostic error indicating
ERROR_FILE_NOT_FOUND using wine's builtin of version.dll and msi.dll,
but ERROR_RESOURCE_DATA_NOT_FOUND using wine's builtin of msi.dll and
native version.dll.
... version.dll's GetFileVersionInfoSizeW does return
ERROR_FILE_NOT_FOUND when trying to get the version of a file that
does not contain a version (for example, a text file). This is
because it relies on VERSION_GetFileVersionInfo_16 to do the file
existance check, which returns 0 (meaning file does not exist) if
LoadLibrary16 fails.
The patch addresses this by making VERSION_GetFileVersionInfo_16
return 0xFFFFFFFF (meaning file exists but does not have version) if
LoadLibrary16 returns an error beside ERROR_FILE_NOT_FOUND.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.