July 2021 - Wine-Bugs - list.winehq.org

[Bug 40220] New: Visual Studio Community 2015 install stuck at splash screen
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

https://bugs.winehq.org/show_bug.cgi?id=40220 Bug ID: 40220 Summary: Visual Studio Community 2015 install stuck at splash screen Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: staal1978(a)gmail.com Distribution: --- In a clean 32-bit WINEPREFIX, I installed dotnet452 / corefonts (appdb indicate that dotnet4 is needed) I mounted the offline install media (vs2015.com_enu.iso) with fuseiso and ran vs_community.exe The installer starts until the grey splash screen saying Visual Studio Community 2015 but never goes further than that. Console output is an endless string of : "fixme:thread:__syscall_NtQueryInformationThread info class 16 not supported yet" -- 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.

2 5

[Bug 37272] New: CheatEngine 6.4 fails after remote process 'breakin', reporting 'Debugger Crash:Access violation (Last location:41)'
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

https://bugs.winehq.org/show_bug.cgi?id=37272 Bug ID: 37272 Summary: CheatEngine 6.4 fails after remote process 'breakin', reporting 'Debugger Crash:Access violation (Last location:41)' Product: Wine Version: 1.7.26 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, as the summary says. The app works well in general - except when breaking into remote process for debugging (to single step). The app is pretty verbose about its doings, using 'OutputDebugString' API. --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Cheat Engine 6.4 ... $ WINEDEBUG=+tid,+seh,+loaddll,+process,+debugstr wine ./Cheat\ Engine.exe >>log.txt 2>&1 ... 0023:warn:debugstr:OutputDebugStringA "setThreadContext(28, 110, 07E9710C). dr0=0 dr1=0 dr2=0 dr3=0 dr7=400" ... 002b:warn:debugstr:OutputDebugStringA "HandleExceptionDebugEvent:80000004" ... 002b:warn:debugstr:OutputDebugStringA "EXCEPTION_SINGLE_STEP. Dr6=00004000" ... 002b:warn:debugstr:OutputDebugStringA "Handling as a single step event" ... 002b:warn:debugstr:OutputDebugStringA "HandleBreak()" ... 0023:trace:seh:raise_exception code=c0000005 flags=0 addr=0x410464 ip=00410464 tid=0023 0023:trace:seh:raise_exception info[0]=00000001 0023:trace:seh:raise_exception info[1]=d000db06 0023:trace:seh:raise_exception eax=0000000b ebx=044bbc78 ecx=d000dafe edx=001c9071 esi=044bbc74 edi=001c9071 0023:trace:seh:raise_exception ebp=01b8ea5c esp=01b8e9f0 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00210282 0023:trace:seh:call_stack_handlers calling handler at 0x7bc9de17 code=c0000005 flags=0 0023:trace:seh:call_stack_handlers handler at 0x7bc9de17 returned 0 ... --- snip --- The CheatEngine debugger was attached to 'notepad' process. --- snip --- Wine-dbg>info process pid threads executable (all id:s are in hex) 00000027 1 'notepad.exe' 00000022 3 'cheatengine-i386.exe' 00000020 1 'explorer.exe' 0000000e 5 'services.exe' 00000019 3 \_ 'plugplay.exe' 00000012 4 \_ 'winedevice.exe' Wine-dbg>info thread process tid prio (all id:s are in hex) ... 00000022 cheatengine-i386.exe 0000002b 0 00000024 0 00000023 0 00000027 notepad.exe 00000028 0 --- snip --- Running the debugger under a debugger yields the following: --- snip --- Unhandled exception: page fault on write access to 0xd000db06 in 32-bit code (0x00410464). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:00410464 ESP:01b8e9f0 EBP:01b8ea5c EFLAGS:00210282( R- -- I S - - - ) EAX:0000000b EBX:040341a8 ECX:d000dafe EDX:001c9071 ESI:040341a4 EDI:001c9071 Stack dump: 0x01b8e9f0: 000000b0 0000000b 040341a4 000000b0 0x01b8ea00: 0423c2e8 0423c2ec 004105ee 0000004c 0x01b8ea10: 0423c2e8 00410bdd 0000001c 0423c2e8 0x01b8ea20: 00000414 0040fa88 006426a9 0423c2e8 0x01b8ea30: 0410a7f8 00000414 006429b7 0423c2e8 0x01b8ea40: 0410a7f8 006427ad 001b2ba8 00000000 000c: sel=0067 base=00000000 limit=00000000 16-bit --x Backtrace: =>0 0x00410464 in cheatengine-i386 (+0x10464) (0x01b8ea5c) 1 0x007011b4 in cheatengine-i386 (+0x3011b3) (0x01b8ea70) 2 0x0050bc97 in cheatengine-i386 (+0x10bc96) (0x01b8f368) 3 0x0050c155 in cheatengine-i386 (+0x10c154) (0x01b8f6a0) 4 0x0044b868 in cheatengine-i386 (+0x4b867) (0x01b8f6b8) 5 0x00452019 in cheatengine-i386 (+0x52018) (0x01b8f728) 6 0x004fd312 in cheatengine-i386 (+0xfd311) (0x01b8f7ac) 7 0x005013c1 in cheatengine-i386 (+0x1013c0) (0x01b8f824) 8 0x0058ef28 in cheatengine-i386 (+0x18ef27) (0x01b8f898) 9 0x006e7668 in cheatengine-i386 (+0x2e7667) (0x01b8faa8) 10 0x7eb8fb5e WINPROC_wrapper+0x19() in user32 (0x01b8fad8) ... 0x00410464: movl $0x0,0x8(%ecx) --- snip --- The app is open source: https://code.google.com/p/cheat-engine --- snip --- $ svn checkout http://cheat-engine.googlecode.com/svn/trunk/ cheat-engine-read-only --- snip --- 'Last location:41' part of error message gives a hint: htps://code.google.com/p/cheat-engine/source/browse/trunk/Cheat%20Engine/de… --- snip --- procedure TDebugThreadHandler.VisualizeBreak; begin TDebuggerthread(debuggerthread).execlocation:=41; if processhandler.SystemArchitecture=archx86 then MemoryBrowser.lastdebugcontext:=context^ else MemoryBrowser.lastdebugcontextarm:=armcontext; WaitingToContinue:=not lua_onBreakpoint(context); if WaitingToContinue then //no lua script or it returned 0 MemoryBrowser.UpdateDebugContext(self.Handle, self.ThreadId); end; --- snip --- The crashes happens during update of stacktrace listview, after a couple of 'dbghelp.StackWalk64' calls. 'TMemoryBrowser.UpdateDebugContext' -> 'TfrmStacktrace.stacktrace' https://code.google.com/p/cheat-engine/source/browse/trunk/Cheat%20Engine/f… The crash address is an indirect reference from ECX = 0xd000dafe (+8) .. a value which corresponds to Wine's 'frame->KdHelp.KiCallUserMode' magic value. The stack frame data structure passed to 'StackWalk64' is allocated from internal Delphi heap and initialized. --- snip --- procedure TfrmStacktrace.stacktrace(threadhandle:thandle;context:_context); var stackframe: PStackframe64; cxt:_context; wow64ctx: CONTEXT32; a,b,c,d: dword; sa,sb,sc,sd:string; machinetype: dword; cp: pointer; found: boolean; begin ... getmem(stackframe,sizeof(tstackframe)); zeromemory(stackframe,sizeof(tstackframe)); stackframe^.AddrPC.Offset:=context.{$ifdef cpu64}rip{$else}eip{$endif}; stackframe^.AddrPC.mode:=AddrModeFlat; stackframe^.AddrStack.Offset:=context.{$ifdef cpu64}rsp{$else}esp{$endif}; stackframe^.AddrStack.Mode:=addrmodeflat; stackframe^.AddrFrame.Offset:=context.{$ifdef cpu64}rbp{$else}ebp{$endif}; stackframe^.AddrFrame.Mode:=addrmodeflat; ... --- snip --- The corresponding disassembly, annotated: --- snip --- 0050BBD1 8D45 F8 LEA EAX,DWORD PTR SS:[EBP-8] 0050BBD4 BA A4000000 MOV EDX,0A4 ; sizeof(tstackframe) 0050BBD9 E8 323EF0FF CALL cheateng.0040FA10 ; getmem() 0050BBDE 68 A4000000 PUSH 0A4 ; sizeof(tstackframe) 0050BBE3 FF75 F8 PUSH DWORD PTR SS:[EBP-8] 0050BBE6 E8 C5121600 CALL cheateng.0066CEB0 ; zeromemory() 0050BBEB 8B4D F8 MOV ECX,DWORD PTR SS:[EBP-8] 0050BBEE 8B95 38F8FFFF MOV EDX,DWORD PTR SS:[EBP-7C8] 0050BBF4 B8 00000000 MOV EAX,0 0050BBF9 8911 MOV DWORD PTR DS:[ECX],EDX ; stackframe^.AddrPC.. 0050BBFB 8941 04 MOV DWORD PTR DS:[ECX+4],EAX --- snip --- 0xA4 is a bit too small for 'STACKFRAME64' structure. MSDN: http://msdn.microsoft.com/en-us/library/windows/desktop/ms680646%28v=vs.85%… My guess is that Delphi/Pascal's definition of 'tstackframe' doesn't include the 'KDHELP64' part which is reserved for kernel debuggers. The problem is that Wine writes magic values into an area that should be left untouched since we're dealing with usermode debugging. That corrupts the internal heap. Source: http://source.winehq.org/git/wine.git/blob/61a9eef9a1c0a72e6571742dbb830f7b… --- snip --- ... 242 /* we don't handle KdHelp */ 243 frame->KdHelp.Thread = 0xC000FADE; 244 frame->KdHelp.ThCallbackStack = 0x10; 245 frame->KdHelp.ThCallbackBStore = 0; 246 frame->KdHelp.NextCallback = 0; 247 frame->KdHelp.FramePointer = 0; 248 frame->KdHelp.KiCallUserMode = 0xD000DAFE; 249 frame->KdHelp.KeUserCallbackDispatcher = 0xE000F000; 250 frame->KdHelp.SystemRangeStart = 0xC0000000; 251 frame->KdHelp.Reserved[0] /* KiUserExceptionDispatcher */ = 0xE0005000; ... --- snip --- The code that writes the magic values was added 8 years ago: http://source.winehq.org/git/wine.git/commitdiff/558130a696a1e6c11a84f3d1f1… Not sure what the intention was since usermode debuggers can't deal with these things anyway. With that part fixed, CheatEngine can debug remote processes after attaching. $ sha1sum CheatEngine64.exe 8cb06bca312ed2bfa02c7f9344f2717d02ecd931 CheatEngine64.exe $ du -sh CheatEngine64.exe 8.7M CheatEngine64.exe $ wine --version wine-1.7.26-44-gb10b391 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.

2 5

[Bug 31322] New: Remote Tools for Visual Studio 2012 RC for Windows on ARM (WoA) crashes because TPIDRURW (user TLS register) TEB value is not preserved by kernel
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=31322 Bug #: 31322 Summary: Remote Tools for Visual Studio 2012 RC for Windows on ARM (WoA) crashes because TPIDRURW (user TLS register) TEB value is not preserved by kernel Product: Wine Version: 1.5.9 Platform: arm OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, split off from bug 31308 (see there for details). TPIDRURW (user TLS register) TEB value is not preserved by kernel (currently either reset to zero or left with same values across context switches). 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.

2 15

[Bug 31308] New: Remote Tools for Visual Studio 2012 RC for Windows on ARM (WoA) crashes due to invalid user TLS register value access
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=31308 Bug #: 31308 Summary: Remote Tools for Visual Studio 2012 RC for Windows on ARM (WoA) crashes due to invalid user TLS register value access Product: Wine Version: 1.5.9 Platform: arm OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, for André, some toy to play with ;-) "Remote Tools for Visual Studio 2012 RC" for Windows on ARM (WoA) can be downloaded here: http://www.microsoft.com/visualstudio/11/en-us/downloads#remote-tools It crashes on my quad Cortex-A9 based i.mx6 Sabre with Ubuntu Linux 12.04 --- snip --- Unhandled exception: page fault on read access to 0xc2083992 in 32-bit code (0x00419d44). Register dump: Thumb User Mode Pc:419d44 Sp:4134f720 Lr:418ed1 Cpsr:200f0030(--C-) r0:0208 r1:0001 r2:4134f7c8 r3:0208 r4:c208398a r5:4134f7c8 r6:0000 r7:4134f728 r8:dddd r9:04e4 r10:0100 Fp:4134f758 Ip:4134f518 Stack dump: 0x4134f720: 00000000 00000000 4134f7c8 00000100 0x4134f730: 00000001 8161b1cd 4134f748 00000100 0x4134f740: 4134f7c8 00000001 4134fd38 00446530 0x4134f750: 000004e4 4006e000 4134f790 00418f91 0x4134f760: 4134fac8 000004e4 00000000 00000000 0x4134f770: 00446998 00446308 42164138 40a72801 Backtrace: =>0 0x00419d44 in rtools_setup_arm (+0x19d44) (0x4134f758) 1 0x00418ed1 in rtools_setup_arm (+0x18ed0) (0x4134f758) 0x00419d44: ldr r4, [r4, #8] Modules: Module Address Debug info Name (77 modules) ELF 8000- 12000 Deferred <wine-loader> PE 400000- 454000 Export rtools_setup_arm ELF 40031000-4003f000 Deferred libsm.so.6 ... System information: Wine build: wine-1.5.9-186-g1f6febe Platform: arm Host system: Linux Host version: 3.2.0-1000-linaro-lt-mx6 --- snip --- WINEDEBUG=+tid,+seh,+relay doesn't reveal much, might be app init/startup code: --- snip --- $ wine ./rtools_setup_arm.exe ... 0024:Call KERNEL32.GetLastError() ret=00416973 0024:Ret KERNEL32.GetLastError() retval=00000000 ret=00416973 0024:Call KERNEL32.MultiByteToWideChar(000004e4,00000001,4130f7c8 " \x01\x02\x03\x04\x05\x06\x07\x08\t\n\x0b\x0c\r\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f !\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~\x7f\x80\x81\x82\x83\x84\x85\x86\x87\x88\x89\x8a\x8b\x8c\x8d\x8e\x8f\x90\x91\x92\x93\x94"...,00000100,00000000,00000000) ret=00418e95 0024:Ret KERNEL32.MultiByteToWideChar() retval=00000100 ret=00418e95 0024:trace:seh:raise_exception info[0]=00000000 0024:trace:seh:raise_exception info[1]=c2083992 0024:trace:seh:raise_exception Pc:419d44 Sp:4130f720 Lr:418ed1 Cpsr:200f0030 r0:0208 r1:0001 r2:0100 r3:0208 0024:trace:seh:raise_exception r4:c208398a r5:4130f7c8 r6:0000 r7:4130f728 r8:dddd r9:04e4 r10:0100 Fp:4130f758 Ip:4130f518 0024:trace:seh:call_stack_handlers calling handler at 0x403e3900 code=c0000005 flags=0 0024:Call KERNEL32.UnhandledExceptionFilter(4130f574) ret=403e3964 wine: Unhandled page fault on read access to 0xc2083992 at address 0x419d44 (thread 0024), starting debugger... 0024:trace:seh:start_debugger Starting debugger "winedbg --auto 35 68" ... --- snip --- Winedbg's builtin disassembler isn't really helpful, it's missing various thumb(2) opcodes. Fortunately there is a free IDA 6.2 demo version for Linux which also supports ARM family for download: http://www.hex-rays.com/products/ida/support/download_demo.shtml This is an invaluable tool which can be used to improve winedbg's disassembler and investigate other problems on ARM. The code in question: --- snip --- ... .text:00419D40 MRC p15, 0, R4,c13,c0, 2 .text:00419D44 LDR R4, [R4,#8] ... --- snip --- ARM info center CP15 c13 register summary: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0388f/CIHFGF… Another resource: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0360f/CACEAI… Opcode_2=3 register "TPIDRURO" is actually ARM HW TLS register, used by libc (__get_tls()). Opcode_2=2 register "TPIDRURW" is "Software Thread ID, User, R/W" Not sure if this is a "free for use" register or if any user space threading library code actually manages this register. One would have to search eglibc sources for ARM and any userspace libraries mapped into process address space, not part of Wine. The values don't seem very random but they point to invalid (not mapped) memory locations. I couldn't find any MCR opcodes in application code, so it's probably written elsewhere. This linux kernel patch has a bit of information: http://www.kernelhub.org/?p=2&msg=57979 It got committed to Linux 3.3.5: http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.3.5 (search for TPIDRURW). I'm running 3.2.0 so it's obviously not cleared by kernel side on context switch. Anyway, I fear this will be most likely upstream if the kernel deliberately clears it on every context switch (starting with 3.3.5). $ du -sh rtools_setup_arm.exe 16M rtools_setup_arm.exe $ sha1sum rtools_setup_arm.exe 6f75e6dad60b64e1f074884829b63ca00bcdb531 rtools_setup_arm.exe 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.

2 22

[Bug 37915] New: IsWow64Process fix(es) required: 32bit UPlay games do not launch in a 64Bit prefix when Wine is set to Vista/Win7
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

https://bugs.winehq.org/show_bug.cgi?id=37915 Bug ID: 37915 Summary: IsWow64Process fix(es) required: 32bit UPlay games do not launch in a 64Bit prefix when Wine is set to Vista/Win7 Product: Wine Version: 1.7.34 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Distribution: --- While the recent commit http://source.winehq.org/git/wine.git/commitdiff/bfd088dbc6b4f397d9adfbc11a… now allows Uplay to launch 64-bit games in a 64-bit prefix when Windows 7 is selected (and probably Vista and 8), it doesn't help with launching 32-bit games. Since #33776 was closed without covering this situation, I'm opening this bug to cover that use-case here. Attachment 50492 from #33776 (https://bugs.winehq.org/attachment.cgi?id=50492&action=diff) solves this for me, but seems to be a work in progress based on what the author has said there. This issue is also perhaps not specific to Uplay, although I don't know of any other application affected by the bugs in the existing implementation at this time (hence the title). -- 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.

2 12

[Bug 39101] New: Visual Studio Compiler creates invalid interface from a typelib
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

https://bugs.winehq.org/show_bug.cgi?id=39101 Bug ID: 39101 Summary: Visual Studio Compiler creates invalid interface from a typelib Product: Wine Version: 1.7.49 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- Created attachment 52094 --> https://bugs.winehq.org/attachment.cgi?id=52094 Sample Project winetricks vc2008express Open the Attached project and compile. StdAfx.h has line. #import "../typelibs/Debug/typelibs.tlb" which causes the compiler to get generate typelibs.tlh and typelibs.tli files. These files represent the interfaces that are defined in the TLB. Under WINE, the file created (runme\Debug\typelibs.tlh), contains a line, like below, for every function in the base interfaces(s). virtual HRESULT _VtblGapPlaceholder1( ) { return E_NOTIMPL; } whereas on windows these lines aren't there. These extra lines cause the V Table to be incorrect and programs crash when any of the interface functions are called. -- 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.

2 8

[Bug 33221] New: Visual Studio 2008 (9.0) Express Edition cannot compile with builtin msvcr90
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=33221 Bug #: 33221 Summary: Visual Studio 2008 (9.0) Express Edition cannot compile with builtin msvcr90 Product: Wine Version: 1.5.25 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: msvcrt AssignedTo: wine-bugs(a)winehq.org ReportedBy: ehoover(a)mines.edu Classification: Unclassified Regression SHA1: 5d88f780dd4bbbde0ff27075b58321d7347f6d4b The VS IDE terminal window shows the following error: 1>cl : Command line warning D9002 : ignoring unknown option '/' 1>cl : Command line error D8003 : missing source filename A git bisect reveals: 5d88f780dd4bbbde0ff27075b58321d7347f6d4b is the first bad commit commit 5d88f780dd4bbbde0ff27075b58321d7347f6d4b Author: Piotr Caban <piotr(a)codeweavers.com> Date: Mon Feb 18 10:26:01 2013 +0100 msvcr90: Prefer builtin version. :040000 040000 09577625ae5788cd73d4a3cd6c5c6f82ea7d9807 aef32f8a1984759761461627 A debug trace for +msvcrt is quite large (rather obviously), but can be found here: https://dl.dropbox.com/u/195059/wine/msvcrt.log The issue can be worked around by setting msvcr90 to native in winecfg. -- 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.

2 8

[Bug 33207] New: Visual Studio 2008 (9.0) Express Edition cannot launch in a fresh prefix
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=33207 Bug #: 33207 Summary: Visual Studio 2008 (9.0) Express Edition cannot launch in a fresh prefix Product: Wine Version: 1.5.25 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: ehoover(a)mines.edu Classification: Unclassified On launch the application reports "The application data folder for <program> could not be created." (e.g. "Visual C++ Express"). By manually creating the expected folder the problem can be worked around: mkdir ${HOME}/.wine/drive_c/users/${USER}/Application\ Data -- 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.

2 10

[Bug 15619] New: Visual Studio 2008 Installer Hangs after err:seh:setup_exception_record stack overflow
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=15619 Summary: Visual Studio 2008 Installer Hangs after err:seh:setup_exception_record stack overflow Product: Wine Version: 1.1.6 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: peterbelm(a)gmail.com Created an attachment (id=16642) --> (http://bugs.winehq.org/attachment.cgi?id=16642) Terminal output When running the Visual Studio 2008 installer the setup window appears, and starts loading installation components, after about 30 seconds full processor usage, err:seh:setup_exception_record stack overflow appears in the terminal output (see attachment) the progress bar increases slightly, and then it seems to hang. Checking with strace on the setup.exe process (the main one, the other one gives me 'Operation not permitted', even when sudo'ing it) shows it is waiting to read from a pipe, which is red when doing 'ls -l', I assume that means the pipe doesn't exist any more? -- 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.

2 6

[Bug 29905] New: Microsoft Visual Studio 2008: attaching to process fails with "unknown error: 0x80070003" (support of "Session" namespace for named objects needed)
by wine-bugs＠winehq.org July 19, 2021

July 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=29905 Bug #: 29905 Summary: Microsoft Visual Studio 2008: attaching to process fails with "unknown error: 0x80070003" (support of "Session" namespace for named objects needed) Product: Wine Version: 1.4-rc3 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: wineserver AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, prerequisite: 'winetricks -q dotnet30' Unfortunately for installation of Visual Studio 2008 Professional/Enterprise editions you have to resort to hacks. NOTE: Remote debugging capability is not available in Visual Studio 2005/2008 express editions (free for download). Bug 29354 (installer fails due to ProductID being set during client side "ValidateProductID" standard action -> don't set property) Bug 10601 (GAC API for managed assembly installation needs reparse point/junction API support -> force msi_install_assembly()/IAssemblyCache_InstallAssembly to succeed on failure) The installer still fails in the end but it's enough to have a "half" usable IDE/build environment (.NET Framework 3.5 and some .NET service packs get skipped due to Mono registry/fake mess while other components fail to install). Unlike Visual Studio 2005 which uses wtsapi (bug 29903), Visual Studio 2008 retrieves the process list by different means and displays the process in "standard" transport mode. --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Microsoft Visual Studio 9.0/Common7/IDE $ wine ./devenv.exe --- snip --- 1) Menu "extras" -> "attach to process" 2) select one process, click "attach" It starts the debugging environment but fails half-through with "unknown error: 0x80070003" --- snip --- ... 0082:Call KERNEL32.ProcessIdToSessionId(00000085,0032e5f0) ret=3f083224 0082:Ret KERNEL32.ProcessIdToSessionId() retval=00000001 ret=3f083224 ... 0082:Call KERNEL32.CreateFileMappingW(ffffffff,0032e604,00000004,00000000,0000003c,0032e610 L"Session\\0\\Microsoft_VS90_causality_sharedmemory-133") ret=3f089149 0082:Ret KERNEL32.CreateFileMappingW() retval=00000000 ret=3f089149 0082:Call KERNEL32.GetLastError() ret=3f08897a 0082:Ret KERNEL32.GetLastError() retval=00000003 ret=3f08897a ... 0082:Call KERNEL32.FormatMessageW(00001300,00000000,80070003,00000400,0032e638,00000000,00000000) ret=3f2b9072 0082:Ret KERNEL32.FormatMessageW() retval=00000000 ret=3f2b9072 ... 0082:Call oleaut32.SysAllocString(03d19b60 L"Der Vorgang wird nicht unterst\00fctzt. Unbekannter Fehler: 0x80070003.") ret=3f247a9f ... --- snip --- For communication between target and debugger a shared memory location is created. The shared memory (file mapping) is created using a special namespace syntax: "Session\\0\\Microsoft_VS90_causality_sharedmemory-133" Wineserver doesn't support "Session\<id>" yet, hence CreateFileMappingW() fails. (another run with +server): --- snip --- 0009: create_mapping( access=000f000f, attributes=00000080, protect=00000043, size=0000003c, file_handle=0000, objattr={rootdir=0010,sd={control=00000004,owner=<not present>,group=<not present>,sacl={},dacl={{AceType=ACCESS_ALLOWED_ACE_TYPE,Mask=10000000,AceFlags=0,Sid={S-1-5-21-0-0-0-1000}}}},name=L"Session\\0\\Microsoft_VS90_causality_sharedmemory-18"} ) 0009: create_mapping() = OBJECT_PATH_NOT_FOUND { handle=0000 } --- snip --- Source: http://source.winehq.org/git/wine.git/blob/ba715798094896e8b98fc5803e16b00f… "Kernel Object Namespaces": http://msdn.microsoft.com/en-us/library/aa382954.aspx --- quote --- ... In addition to the "Global\" prefix, client processes can use the "Local\" prefix to explicitly create an object in their session namespace. These keywords are case sensitive. The "Session\" prefix is reserved for system use and you should not use it in names of kernel objects. ... <user comments> This documentation effectively states that 'Global', 'Local' and 'Session' are all valid as name prefixes (but not as names). There appears to be no documentation that says 'Session' cannot be used as a prefix or that it is reserved for use as a prefix. By referring to 'Session' as it does, it strongly implies that this a fully legal and valid way to enable applications in one session to interact with applications in another session. I think Microsoft should consider adding more detail about whether 'Session' is or is not valid for use by developers, and if so exactly what it can and cannot be used for. [user reponse] Global\ refers to the Global Namespace, Local\ refers to the current session's namespace, Session\x\ refers to x's namespace where x is the session id (not LUID or anything special, just a counter) --- quote --- "Memory mapped files from XP to Vista" http://blogs.msdn.com/b/maartenb/archive/2008/05/07/memory-mapped-files-fro… --- quote --- ... Online search for "sessions\1\basenamedobject" gives hits that point to Terminal Services. There appear to be Local Global and Session namespaces. So prior to Vista and Server 2008 all services shared the same namespace as the first user logging in to the machine. This was session 0. With Vista this is no longer the case. Just like all compatibility issues it is explained in the cookbook. --- quote --- There is a workaround for this problem. You can force a "normal" shared memory mapping name by setting to WinVer to "Windows 2000" prior running the IDE. Some components don't really support running WinVer < "Windows XP" anymore hence this might break some stuff (VS2008 refuses to install with W2K mode). At least this prevents the error message when attaching. It doesn't really break/pause the remote process (might be bug 25462). 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.

2 10