wine-bugs February 2016

wine-bugs@winehq.org

1 participants
7478 discussions

[Bug 39671] New: Wine 1.7.55 regression: buttons no longer visible
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=39671 Bug ID: 39671 Summary: Wine 1.7.55 regression: buttons no longer visible Product: Wine Version: 1.7.55 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: scarre.lu(a)gmail.com Distribution: --- Buttons with images are no longer visible in several desktop applications previously running fine under wine 1.7: * SplashID desktop * Most Delphi applications using speedbutton instances The buttons are invisible, although clicking (blindly) on their supposed position reveals them. -- 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 7

[Bug 40095] New: Photos opened in Nikon Capture NX 2.4.7 have inverted red and blue channel for displaying.
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=40095 Bug ID: 40095 Summary: Photos opened in Nikon Capture NX 2.4.7 have inverted red and blue channel for displaying. Product: Wine Version: 1.9.3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wylda(a)volny.cz Distribution: --- I re-tested bug 33140, which was recelntly closed as fixed. Maybe it was fixed just for RAW. Anyway, it is not fixed in wine-1.9.3 and default JPGs. Steps: 1. winetricks dotnet40 corefonts gdiplus 2. set win version to Vista 3. install NX2 4. run the app and open: c:\Program Files\Nikon\Capture NX 2\html\images\common\13redeyecp_02_nx20.jpg Instead of human color you will see bluish face. -- 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 7

[Bug 36319] New: valgrind shows several possible leaks in quartz/tests/misc.c
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=36319 Bug ID: 36319 Summary: valgrind shows several possible leaks in quartz/tests/misc.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48405 --> https://bugs.winehq.org/attachment.cgi?id=48405 valgrind log ==27568== 5,744 bytes in 148 blocks are possibly lost in loss record 643 of 655 ==27568== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==27568== by 0x4ECBA52: alloc_bstr (oleaut.c:162) ==27568== by 0x4ECC255: SysAllocStringByteLen (oleaut.c:413) ==27568== by 0x4EF7C4F: ITypeLib2_Constructor_MSFT (typelib.c:2254) ==27568== by 0x4EFB20B: LoadTypeLibEx (typelib.c:3460) ==27568== by 0x4EFCDF2: LoadTypeLib (typelib.c:454) ==27568== by 0x4EFD4AA: LoadRegTypeLib (typelib.c:537) ==27568== by 0x647CAD3: ??? ==27568== by 0x6483475: ??? ==27568== by 0x6413806: ??? ==27568== by 0x6413AC0: ??? ==27568== by 0x53134DD: CoCreateInstance (unknwn.h:226) ==27568== by 0x64832A8: ??? ==27568== by 0x6486644: ??? ==27568== by 0x641A819: ??? ==27568== by 0x6413AC0: ??? ==27568== by 0x53134DD: CoCreateInstance (unknwn.h:226) ==27568== by 0x4D6F01A: test_aggregation (misc.c:81) ==27568== by 0x4D70125: func_misc (misc.c:174) ==27568== by 0x4D723D4: run_test (test.h:584) ==27568== ==9329== 288 bytes in 2 blocks are definitely lost in loss record 485 of 657 ==9329== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==9329== by 0x654C126: ??? ==9329== by 0x6544704: ??? ==9329== by 0x64ECFB7: ??? ==9329== by 0x64E7667: ??? ==9329== by 0x53134DD: CoCreateInstance (unknwn.h:226) ==9329== by 0x4D6F01A: test_aggregation (misc.c:81) ==9329== by 0x4D70125: func_misc (misc.c:174) ==9329== by 0x4D723D4: run_test (test.h:584) ==9329== by 0x4D727C3: main (test.h:654) ==9329== etc. -- 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 4

[Bug 39512] New: Make it possible to run multiple tests in a single task
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=39512 Bug ID: 39512 Summary: Make it possible to run multiple tests in a single task Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Currently when a patch touches multiple tests the TestBot creates one task per test per VM, and even multiple jobs if the patch touches tests for multiple dlls. For instance currently Wine patches are tested on four 32 bit VMs and five 64 bit VMs. So a patch that modified 2 tests in one dll and 3 in another would create 2 jobs and 72 tasks (2 build tasks, (2+3)*(4+5) 32 bit tasks, and (2+3)*5 64 bit tasks). The overall run time would obviously be quite long, thus earning this type of (otherwise quite legitimate) patch the 'test bomb' nickname. The fix is to take the ability to build a WineTest executable with only a few tests (see bug 39065) further so that: * A WineTest executable containing only the modified tests is built. * The TestBot then creates only one job and one task per VM to run that test executable. * Just like in bug 39065 the tasks would have to specify a command line such that only the modified tests are run. That's not just for efficiency's sake but also to avoid getting test failures from unmodified tests. * Instead of having a constant 2 minutes timeout the tasks would also need to have a timeout that's in line with the number of tests to run. This could be something like: MIN(tests_count, 2) * 2 minutes + average_time * tests_count Where average_time would be some configurable constant (probably something around 3 to 5 seconds). -- 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 37612] New: Mount & Blade: Crashes on startup (No compatible Direct3D Device)
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=37612 Bug ID: 37612 Summary: Mount & Blade: Crashes on startup (No compatible Direct3D Device) Product: Wine Version: 1.7.31 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: m22mail(a)comcast.net Mount & Blade: Warband crashes after the intro video with the error popup "Could not find any compatible 3D device". The game runs in Wine version 1.7.9 however it seems all the latest versions crash with this error. I installed all the DirectX .dlls from winecfg and installed the latest DirectX 9.0 Redistributable, but the crash remains. It seems as though this error happens when a video card does not meet the requirements, however I can confirm my card does meet the requirements, being that it opens in older versions of Wine. -- 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 11

[Bug 38290] New: LabVIEW installer (2009sp1, 2012 Fall, 2014 Fall) fails with msi.dll ACCESS_VIOLATION
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=38290 Bug ID: 38290 Summary: LabVIEW installer (2009sp1, 2012 Fall, 2014 Fall) fails with msi.dll ACCESS_VIOLATION Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: enrico.segre(a)weizmann.ac.il Distribution: --- when setup.exe is run from desktop without particular wineprefix, as I reported for the AppDB ( https://appdb.winehq.org/objectManager.php?sClass=application&iId=4556 ). I see that several other bugs related to msi and labview (5399, 8895, 26537, 27841, 28849, 29099 for example) have already been filed and closed, so forgive if that is a duplicate, or if there is a trivial workaround which I ignore. -- 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 35033] New: Alpha Protocol: Game hangs with black screen at startup
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=35033 Bug #: 35033 Summary: Alpha Protocol: Game hangs with black screen at startup Product: Wine Version: 1.7.7 Platform: Other OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ipickert55(a)gmail.com Classification: Unclassified Created attachment 46703 --> http://bugs.winehq.org/attachment.cgi?id=46703 Wine Log Game just sits there with a black screen, no sound or menus or anything. -- 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 12

[Bug 36801] New: Crash during program install
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=36801 Bug ID: 36801 Summary: Crash during program install Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mike99(a)live.co.uk Created attachment 48876 --> http://bugs.winehq.org/attachment.cgi?id=48876 Contains data produced by 'Show Details' button in error box. When trying to install BearShare, the BearShare installation box opens followed by Program Error box with the error ' BearShareSetup-r0-n-bf.exe has encountered a serious problem...' I have attached a copy of the data produced by the 'Show Details' button. -- 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 29252] New: ICBC Internet Banking Assistant ICBCEBankAssist.exe can't open embed iexplore
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=29252 Bug #: 29252 Summary: ICBC Internet Banking Assistant ICBCEBankAssist.exe can't open embed iexplore Product: Wine Version: 1.3.34 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Classification: Unclassified Created attachment 37828 --> http://bugs.winehq.org/attachment.cgi?id=37828 Log: start ICBC Assistant wine-1.3.34-39-g95f81d1 1. Download ICBC Internet Banking Assistant installer ( ICBCSetupIntegration.msi ) from https://mybank.icbc.com.cn/icbc/enperbank/index.jsp $ wget http://www.icbc.com.cn/icbc/html/download/EbankToolsSoftware/ICBCSetupInteg… 2. install ICBC Internet Banking Assistant $ msiexec /i ICBCSetupIntegration.msi 3. Start Internet Banking Assistant cd to "Program Files/ICBCEbankTools/ICBCSetupIntegration" $ wine ICBCEBankAssist.exe 4. Click on "One-key Installation for Non-USBKey User" Expect result: open a embed iexplore, user can install ActiveX controls from the Assistant Actual result: nothing happen winetricks wininet doesn't work, winetricks ie7 doesn't work -- 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 7

[Bug 25579] New: Microsoft Flight Simulator X: cannot activate product
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=25579 Summary: Microsoft Flight Simulator X: cannot activate product Product: Wine Version: 1.3.9 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Terminal shows some wininet fixme's: fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! so I tried native wininet, no dice. Next was a winhttp error: err:winhttp:netconn_secure_connect couldn't verify server certificate (12057) so 'winetricks winhttp'. Still no luck: austin@aw21 ~/.wine/drive_c/Program Files/Microsoft Games/Microsoft Flight Simulator X $ wine fsx.exe fixme:heap:HeapSetInformation 0x750000 0 0x32f36c 4 fixme:heap:HeapSetInformation 0x110000 0 0x32f368 4 fixme:heap:HeapSetInformation 0x330000 0 0x32f364 4 fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub! fixme:ras:RasEnumConnectionsW (0x204b90,0x1e1e454,0x1fd2004),stub! fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program to use LAN connection/winsock instead! fixme:secur32:schan_InitializeSecurityContextW Using hardcoded "NORMAL" priority fixme:wintrust:HTTPSCertificateTrust (0x1ef968) fixme:wintrust:HTTPSFinalProv (0x1ef968) didn't try beyond that. -- 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 9

[Bug 38159] New: NULL pointer dereferencing
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=38159 Bug ID: 38159 Summary: NULL pointer dereferencing Product: Wine Version: 1.7.37 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Distribution: --- File /dlls/krnl386.exe16/int2f.c Lines 1026-1034 if (!driver_request) { /* FIXME - to be deleted ?? */ ERR("ES:BX==0 ! SEGFAULT ?\n"); ERR("-->BX=0x%04x, ES=0x%04x, DS=0x%04x, CX=0x%04x\n", BX_reg(context), context->SegEs, context->SegDs, CX_reg(context)); driver_request[4] |= 0x80; driver_request[3] = 5; /* bad request length */ return; } If driver_request == NULL then driver_request[4] will be NULL pointer dereferencing. -- 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 4

[Bug 29849] New: oleaut32's OLEPictureImpl_Load fails when Stat() method is missing
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=29849 Bug #: 29849 Summary: oleaut32's OLEPictureImpl_Load fails when Stat() method is missing Product: Wine Version: 1.4-rc2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: oleaut32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: michael.blumenkrantz(a)gmail.com Classification: Unclassified Created attachment 38772 --> http://bugs.winehq.org/attachment.cgi?id=38772 test case Without a Stat() method, this function should only read the parts of a file that are needed. Instead, it continues to read and eventually crashes. Find attached a test case which takes an image file as an argument, then crashes. -- 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 23

[Bug 38356] New: Xibo Player 1.7.3: Cant start
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=38356 Bug ID: 38356 Summary: Xibo Player 1.7.3: Cant start Product: Wine Version: 1.7.40 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: ignacio.santolin(a)gmail.com Distribution: --- Created attachment 51200 --> https://bugs.winehq.org/attachment.cgi?id=51200 Xibo debug I Installed http://xibo.org.uk/get-xibo/ "Xibo For Windows" And When i tries to start, shows the attached debug and cant start -- 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 7

[Bug 36633] New: Administrative privileges not sufficient
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=36633 Bug ID: 36633 Summary: Administrative privileges not sufficient Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 9728889999o(a)gmail.com Created attachment 48676 --> http://bugs.winehq.org/attachment.cgi?id=48676 Error Message I tried to run an application under Wine and it says that I have "insufficient privileges, please close and run again as administrator." I tried to run the Windows 7 USB/DVD Creator. See the attachment for more. -- 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 39306] New: wine crash when using Lord of the rings : battle for middle earth 2
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=39306 Bug ID: 39306 Summary: wine crash when using Lord of the rings : battle for middle earth 2 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: titouan.dugre(a)gmail.com Distribution: --- Wine gives this message : "direct 3 D error 0*80004001 (E_NOTIMPL) 14 adresses : (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) (0):(unknow mind) (unknow) -- 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 37067] New: System.NotSupportedException: CodePage 1361 not supported
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=37067 Bug ID: 37067 Summary: System.NotSupportedException: CodePage 1361 not supported Product: Wine Version: 1.7.22 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: t_arceri(a)yahoo.com.au Gemini Script Editor crashes when trying to open a script. With the following exception thrown. The scripts are from rpgmaker I think it might use Korean as a was to try obfuscate the script Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for ScintillaNet.Scintilla ---> System.NotSupportedException: CodePage 1361 not supported at System.Text.Encoding.GetEncoding (Int32 codepage) [0x00000] in <filename unknown>:0 -- 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 35927] New: Win Toolkit v.1.4.37.20 requires administrative privilegies on startup.
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=35927 Bug ID: 35927 Summary: Win Toolkit v.1.4.37.20 requires administrative privilegies on startup. Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sov.info(a)mail.ru Created attachment 47977 --> http://bugs.winehq.org/attachment.cgi?id=47977 screenshot I tried to login as root and run wine, but this error still present. You can see it on screenshot... Ubuntu 14.04 beta x64, wine x86-x64, ver. 1.6.2 from proposed. -- 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 7

[Bug 36434] New: Regression: Capture NX-D fails with "Initialization error (E010)"
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=36434 Bug ID: 36434 Summary: Regression: Capture NX-D fails with "Initialization error (E010)" Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fordfrog(a)fordfrog.com i'm using latest wine from source repository. this bug is probably week or so old. when launching Nikon Capture NX-D, it fails with "Initialization error (E010)". i have wine compiled with both 32bit and 64 versions (using gentoo live ebuild), but for the app i am using 32 bit version (64bit version does not work due to some missing implementation in wine). i'm running the app using following command: WINEPREFIX=~/.wine32 WINEARCH=win32 wine .wine32/drive_c/Program\ Files/Nikon/Capture\ NX-D/Module/CaptureNX-D.exe .wine32 directory is initialized for 32bit arch and windows 8. before week or so the app started without any issue and it was usable. but few days ago it stopped to launch. this is the output before the bug occurs: $ WINEPREFIX=~/.wine32 WINEARCH=win32 wine .wine32/drive_c/Program\ Files/Nikon/Capture\ NX-D/Module/CaptureNX-D.exe fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33fbcc 1 C) semi-stub fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:thread:GetThreadPreferredUILanguages 52, 0x33f9c0, 0x33fa30 0x33f9c8 fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33edc0 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33ee50 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33ec80 1 C) semi-stub fixme:msvcrt:__clean_type_info_names_internal (0x788b0e54) stub fixme:msvcrt:__clean_type_info_names_internal (0x1001e33c) stub fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub the complete process of installation and running is the same as in bug #35864. -- 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 7

[Bug 39996] New: Application Autodata will not load icons and text
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=39996 Bug ID: 39996 Summary: Application Autodata will not load icons and text Product: Wine Version: 1.7.54 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tutonis(a)gmail.com Distribution: --- Created attachment 53438 --> https://bugs.winehq.org/attachment.cgi?id=53438 It works with wine 1.7.53 After loading application all icons are not show until clicked or focused by keyboard arrow movements. As you can see by pictures there is upper and lower icon regions. After clicking place where icon suppose to be the icon is revealed. The upper icon region gets different icons depending what is being selected. Icons are not redrawn after "revealing" them with mouse or keyboard and changing selection (icons should be redawrn and updated by selected option). The issue is nor present in wine 1.7.53 but happens in 1.7.54 with same configurations. -- 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 7

[Bug 14697] New: wineserver: debug events can block completion of queued user APCs
by wine-bugs＠winehq.org 11 Feb '21

11 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=14697 Summary: wineserver: debug events can block completion of queued user APCs Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, consider the following scenario... A debugger is attached to a debuggee. The debuggee has two threads. The debugger processes debug events and queries virtual memory info of remote process using VirtualQueryEx in its main loop. VirtualQueryEx -> NtQueryVirtualMemory -> enqueues APC_VIRTUAL_QUERY user APC for remote process (debuggee). The calling thread is blocked until the APC is completed. Following is the "good" case: tid=0009 (debugger process, calling thread, main debugger loop) tid=001a (debuggee thread 1) --- snip --- .. 0009: queue_apc( thread=(nil), process=0x54, call={APC_VIRTUAL_QUERY,addr=0x7fff0000} ) 001a: *wakeup* signaled=192 cookie=0x7ffdb7b4 0009: queue_apc() = 0 { handle=0x68, self=0 } 0009: select( flags=4, cookie=0x32d30c, signal=(nil), prev_apc=(nil), timeout=infinite, result={}, handles={0x68} ) 0009: select() = PENDING { apc_handle=(nil), timeout=infinite, call={APC_NONE} } 001a: select( flags=4, cookie=0x7ffdb7b4, signal=(nil), prev_apc=(nil), timeout=1c8f097946d2824 (-0.1787600), result={}, handles={} ) 001a: select() = USER_APC { apc_handle=0x68, timeout=1c8f097946d2824 (-0.1787600), call={APC_VIRTUAL_QUERY,addr=0x7fff0000} } 001a: select( flags=4, cookie=0x7ffdb7b4, signal=(nil), prev_apc=0x68, timeout=1c8f097946d2824 (-0.1792110), result={APC_VIRTUAL_QUERY,status=40000002,base=(nil),alloc_base=(nil),size=0,state=0,prot=0,alloc_prot=0,alloc_type=0}, handles={} ) 0009: *wakeup* signaled=0 cookie=0x32d30c 001a: select() = PENDING { apc_handle=(nil), timeout=1c8f097946d2824 (-0.1792110), call={APC_NONE} } 0009: get_apc_result( handle=0x68 ) 0009: get_apc_result() = 0 { result={APC_VIRTUAL_QUERY,status=40000002,base=(nil),alloc_base=(nil),size=0,state=0,prot=0,alloc_prot=0,alloc_type=0} } --- snip --- Now the interesting one, which ultimately leads to block of calling thread ... tid=0009 (debugger process, calling thread, main debugger loop) tid=001a (debuggee thread 1) tid=001b (debuggee thread 2) --- snip --- 0009: continue_debug_event( pid=0019, tid=001a, status=65538 ) 001a: *wakeup* signaled=258 cookie=0x7ffdb7b4 001b: *wakeup* signaled=258 cookie=0x7ffd77b4 0009: continue_debug_event() = 0 .. 0009: read_process_memory( handle=0x54, addr=0x7ffd8000 ) 001a: *signal* signal=19 0009: read_process_memory() = 0 { data= {} } 0009: read_process_memory( handle=0x54, addr=0x7ffd4000 ) 001a: *signal* signal=19 0009: read_process_memory() = 0 { data={} } 0009: queue_apc( thread=(nil), process=0x54, call={APC_VIRTUAL_QUERY,addr=(nil)} ) 001b: *wakeup* signaled=192 cookie=0x7ed44874 0009: queue_apc() = 0 { handle=0x68, self=0 } 001a: load_dll( handle=(nil), base=0x61090000, size=102400, dbg_offset=0, dbg_size=0, name=0x13e468, filename=L"C:\\windows\\system32\\msacm32.dll" ) 001a: *sent signal* signal=10 001b: *sent signal* signal=10 001a: load_dll() = 0 .. 0009: select( flags=4, cookie=0x32d30c, signal=(nil), prev_apc=(nil), timeout=infinite, result={}, handles={0x68} ) 0009: select() = PENDING { apc_handle=(nil), timeout=infinite, call={APC_NONE} } 001a: set_thread_context( handle=0xfffffffe, flags=00010007, suspend=1, context= {...}) 001a: set_thread_context() = 0 { self=1 } 001b: select( flags=4, cookie=0x7ed44874, signal=(nil), prev_apc=(nil), timeout=infinite, result={}, handles={0x4c} ) 001b: select() = USER_APC { apc_handle=0x68, timeout=infinite, call={APC_VIRTUAL_QUERY,addr=(nil)} } 001a: select( flags=4, cookie=0x7ffdb7b4, signal=(nil), prev_apc=(nil), timeout=0, result={}, handles={} ) 001a: select() = PENDING { apc_handle=(nil), timeout=1c8f09794c8b694 (+0.0000000), call={APC_NONE} } 001b: set_thread_context( handle=0xfffffffe, flags=00010007, suspend=1, context= {...}) 001b: set_thread_context() = 0 { self=1 } 001b: select( flags=4, cookie=0x7ffd77b4, signal=(nil), prev_apc=(nil), timeout=0, result={}, handles={} ) 001b: select() = PENDING { apc_handle=(nil), timeout=1c8f09794c90dc4 (+0.0000000), call={APC_NONE} } ... --- snip --- At this point, tid=0009 (debugger) is blocked forever. When the APC_VIRTUAL_QUERY user APC is queued, remote thread 001b is selected/destined to carry out the APC. After thread 001a and 001b woke up, a dynamic library is loaded from thread 001a which results in LOAD_DLL_DEBUG_EVENT dispatched. This initiates the suspension of all threads in the child process (SIGUSR1 is sent for 001a and 001b). Thread 001a is suspended first, 001b next. The suspension of 001b happens to a time when 001b is about to carry out the APC_VIRTUAL_QUERY. Meanwhile thread 0009 (calling process) is waiting for APC completion result forever because it's blocked by VirtualQueryEx in debugger loop, unable to receive and process any debug event. 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 21

[Bug 10249] New: Battlefield2/SafeDisc 4. x and Punkbuster services cause lockup: child processes debugging misconception
by wine-bugs＠winehq.org 11 Feb '21

11 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=10249 Summary: Battlefield2/SafeDisc 4.x and Punkbuster services cause lockup: child processes debugging misconception Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-kernel AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=8876) --> (http://bugs.winehq.org/attachment.cgi?id=8876) WINEDEBUG=-all,+server,+tid,+loaddll,+seh wine ./BF2.exe +fullscreen 0 +szx 800 +szy 600 &>/tmp/debug_pipe Hello, while testing some PunkBuster stuff on popular games, I came across Battlefield 2 which employs SafeDisc 4.x It seems there is a problem with debuggers in chained child processes. Consider following scenario: --- snip process list --- pid threads parent executable (all id:s are in hex) 0000001b 1 00000008 'PnkBstrA.exe' 0000000c 2 00000008 'explorer.exe' 0000000a 2 00000008 '~e5.0001' 00000008 4 00000000 'BF2.exe' --- snip process list --- --- snip thread list --- process tid prio (all id:s are in hex) 0000001b 0000001c 0 0000000c 00000010 0 0000000d 0 0000000a 00000012 0 0000000b 0 00000008 0000001a 1 00000014 15 00000013 0 00000009 0 --- snip thread list --- "BF2.exe" = parent (game) "~e5.0001" = 1st child = SafeDisc 4.x process = "debugger" "PnkBstrA.exe" = 2nd child = PunkBuster Update Service The 1st child acts as debugger for the parent "BF2.exe" and receives all debug events (process, thread creation, dll load/unload...) There are lots of breakpoint events triggered from parent. This is part of SafeDisc 4.x and used for on-the-fly decryption of code sections (child decrypts code of father). When PunkBuster is initialized (loading of pbcl = client, pbag = agent), the following services should get started: PnkBstrA.exe, PnkBstrB.exe and finally the kmode driver PnkBstrK.exe The service process "PnkBstrA.exe" is started from main process "BF2.exe" (which is a debuggee itself). No debug flags (DEBUG_PROCESS | DEBUG_ONLY_THIS_PROCESS) are specified in process creation flags. The debugger (child of parent, receives the process creation event) does not make debugger_attach() to the newly created child process. The child process seems to inherit the state of being a "debuggee": wine server -> new_process -> set_process_debugger( process, parent->debugger ); The parent got its process->debugger from debugger_attach(). This leads to a problem in child process startup code: "dlls/kernel32/process.c:start_process()" checks the PEB->BeingDebugged field and if set, a system breakpoint is encountered before the entry code is called. This breakpoint results in debug event - seen by debugger. Unfortunately this event is _not_ expected by debugger because it didn't expect another debuggee (child) to be created. Ok, long story short solution: If you debug a process by attaching to an already created process, you _must_ treat default debugging flags as if the process has been created with DEBUG_ONLY_THIS_PROCESS, meaning that all childs created by debuggee will NOT automagically become debuggees. Short and (hopefully) acceptable patch snippet: --- snip --- diff --git a/server/debugger.c b/server/debugger.c index a64a17a..c59f3a0 100644 --- a/server/debugger.c +++ b/server/debugger.c @@ -444,6 +444,7 @@ static int debugger_attach( struct process *process, struct thread *debugger ) resume_process( process ); return 0; } + process->create_flags |= DEBUG_ONLY_THIS_PROCESS; return 1; error: --- snip --- And yes, the patch (snippet) works as intended (tm) ;-) Attached for sake of completeness is relevant server trace. Search for "001c:trace:seh:raise_exception code=80000003 flags=0 addr=0x7b870ed8 " to the point where the entry system breakpoint is triggered. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 17

[Bug 36012] New: OllyDbg 2.x debugger crashes with Wine builtin dbghelp
by wine-bugs＠winehq.org 11 Feb '21

11 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=36012 Bug ID: 36012 Summary: OllyDbg 2.x debugger crashes with Wine builtin dbghelp Product: Wine Version: 1.7.16 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, noticed this a while ago ... reporting now :) Ollydbg v2.x crashes for me with Wine builtin dbghelp. Interestingly the old Ollydbg v1.x doesn't crash with builtin. So I ended up with: Ollydbg 1.x debugging Ollydbg 2.x debugging Wine builtin 'notepad' :) Relevant part of tracelog (with some helper traces added by me): --- snip --- $ WINEDEBUG=+tid,+seh,+dbghelp,+dbghelp_symt wine ./ollydbg.exe >>log2.txt 2>&1 ... 0023:trace:dbghelp_symt:symt_new_function Adding global function L"kernel32<elf>":WCEL_InsertChar @7b83839a-7b8383c8 0023:trace:dbghelp_symt:symt_add_func_local Adding local symbol (L"kernel32<elf>":WCEL_InsertChar): ctx 0x20acd44 0023:trace:dbghelp_symt:symt_add_func_local Adding local symbol (L"kernel32<elf>":WCEL_InsertChar): c 0x20aaba0 0023:trace:dbghelp_symt:symt_add_func_local Adding local symbol (L"kernel32<elf>":WCEL_InsertChar): buffer 0x20ad7f0 ... 0023:trace:dbghelp_symt:symt_add_func_line (0x20ae608)WCEL_InsertChar:0 /home/focht/projects/wine/wine.repo/src/dlls/kernel32/editline.c:328 0023:trace:dbghelp_symt:symt_add_func_line (0x20ae608)WCEL_InsertChar:d /home/focht/projects/wine/wine.repo/src/dlls/kernel32/editline.c:331 0023:trace:dbghelp_symt:symt_add_func_line (0x20ae608)WCEL_InsertChar:15 /home/focht/projects/wine/wine.repo/src/dlls/kernel32/editline.c:332 0023:trace:dbghelp_symt:symt_add_func_line (0x20ae608)WCEL_InsertChar:1b /home/focht/projects/wine/wine.repo/src/dlls/kernel32/editline.c:333 0023:trace:dbghelp_symt:symt_add_func_line (0x20ae608)WCEL_InsertChar:2d /home/focht/projects/wine/wine.repo/src/dlls/kernel32/editline.c:334 ... 0023:trace:dbghelp_symt:symt_new_public Adding public symbol L"kernel32<elf>":WCEL_InsertChar @7b83839a ... 0023:trace:dbghelp:SymMatchStringW L"WCEL_InsertChar" L"*" N 0023:trace:dbghelp_symt:symt_fill_sym_info 0x20ae608 => WCEL_InsertChar 47 7b83839a 0023:trace:dbghelp:send_symbol se->cb=0x7d7f4fd1 se->sym_info=0x335fd8, se->sym_info->Size=47 se->user=0x33683c 0023:trace:dbghelp:sym_enumW sew->cb=0x4c90bc sew->sym_info=0x336848 size=47 sew->ctx=0x337098 0023:trace:dbghelp:SymSetContext Setting same frame {rtn=0 frm=0 stk=0} 0023:trace:dbghelp:symt_enum_locals_helper pair=0x3312fc match=0x7d800bd2 se=0x331398 func=0x20ae608 v=0x20ae63c vlen=4 0023:trace:dbghelp:symt_enum_locals_helper i=0 lsym=0x20ae66c, lsym->tag=0x7 0023:trace:dbghelp:SymMatchStringW L"ctx" L"*" Y 0023:trace:dbghelp_symt:symt_fill_sym_info 0x20ae66c => ctx 4 4 0023:trace:dbghelp:send_symbol se->cb=0x7d7f4fd1 se->sym_info=0x3313b8, se->sym_info->Size=4 se->user=0x331c1c 0023:trace:dbghelp:sym_enumW sew->cb=0x4c8f54 sew->sym_info=0x331c28 size=4 sew->ctx=0x33250c 0023:trace:dbghelp:symt_enum_locals_helper i=1 lsym=0x20ae6e4, lsym->tag=0x7 0023:trace:dbghelp:SymMatchStringW L"c" L"*" Y 0023:trace:dbghelp_symt:symt_fill_sym_info 0x20ae6e4 => c 2 ffffffe0 0023:trace:dbghelp:send_symbol se->cb=0x7d7f4fd1 se->sym_info=0x3313b8, se->sym_info->Size=2 se->user=0x331c1c 0023:trace:dbghelp:sym_enumW sew->cb=0x4c8f54 sew->sym_info=0x331c28 size=2 sew->ctx=0x33250c 0023:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7d7f1208 ip=7d7f1208 tid=0023 0023:trace:seh:raise_exception info[0]=00000000 0023:trace:seh:raise_exception info[1]=00000064 0023:trace:seh:raise_exception eax=00000058 ebx=7d80d000 ecx=003311f0 edx=fffffd6f esi=00000040 edi=0033689c 0023:trace:seh:raise_exception ebp=00331248 esp=00331248 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010202 0023:trace:seh:call_stack_handlers calling handler at 0x4e87c0 code=c0000005 flags=0 --- snip --- 'WCEL_InsertChar' seems to be the offender. Populating the symbol info for that function causes the crash in the debugger callback. http://source.winehq.org/git/wine.git/blob/fc38254fed5dbc07a2a61a2411bfaadc… --- snip --- 327 static void WCEL_InsertChar(WCEL_Context* ctx, WCHAR c) 328 { 329 WCHAR buffer[2]; 330 331 buffer[0] = c; 332 buffer[1] = 0; 333 WCEL_InsertString(ctx, buffer); 334 } --- snip --- During symbol evaluation of second function parameter 'c', the debugger syminfo callback corrupts parts of the caller stack hence the next for-loop iteration 'vector_length(v)' which ought to prepare 'buffer' local symbol info crashes. Source: http://source.winehq.org/git/wine.git/blob/d0665616255ae8b720e14e02072996b7… --- snip --- 909 static BOOL symt_enum_locals_helper(struct module_pair* pair, 910 const WCHAR* match, const struct sym_enum* se, 911 struct symt_function* func, const struct vector* v) 912 { 913 struct symt* lsym = NULL; 914 DWORD pc = pair->pcs->ctx_frame.InstructionOffset; 915 unsigned int i; 916 WCHAR* nameW; 917 BOOL ret; 918 919 for (i=0; i<vector_length(v); i++) 920 { 921 lsym = *(struct symt**)vector_at(v, i); 922 switch (lsym->tag) 923 { ... 933 case SymTagData: 934 nameW = symt_get_nameW(lsym); 935 ret = SymMatchStringW(nameW, match, 936 !(dbghelp_options & SYMOPT_CASE_INSENSITIVE)); 937 HeapFree(GetProcessHeap(), 0, nameW); 938 if (ret) 939 { 940 if (send_symbol(se, pair, func, lsym)) return FALSE; 941 } 942 break; ... 951 } 952 } 953 return TRUE; 954 } --- snip --- Dump of symbol info for second parameter 'c': --- snip --- Wine-dbg>p *se.sym_info {SizeOfStruct=0x58, TypeIndex=0x20a2b90, Reserved={0, 0}, info=0x20a66d4, Size=0x2, ModBase=0x7b810000, Flags=0xd0, Value=0, Address=0xffffffe0, Register=0x15, Scope=0, Tag=0x7, NameLen=0x1, MaxNameLen=0x7d0, Name=""} --- snip --- Flags: 0xD0 = SYMFLAG_LOCAL | SYMFLAG_PARAMETER | SYMFLAG_REGREL Register: 0x15 = CV_REG_ESP Disassembly of 'WCEL_InsertChar': --- snip --- $ objdump -d editline.o 00000cba <WCEL_InsertChar>: cba: 55 push %ebp cbb: 89 e5 mov %esp,%ebp cbd: 83 ec 28 sub $0x28,%esp cc0: 8b 45 0c mov 0xc(%ebp),%eax ; parameter 'c' cc3: 66 89 45 e4 mov %ax,-0x1c(%ebp) ; 'c' as stack variable cc7: 0f b7 45 e4 movzwl -0x1c(%ebp),%eax ccb: 66 89 45 f4 mov %ax,-0xc(%ebp) ; buffer[0] = c ccf: 66 c7 45 f6 00 00 movw $0x0,-0xa(%ebp) ; buffer[1] = 0 cd5: 8d 45 f4 lea -0xc(%ebp),%eax cd8: 89 44 24 04 mov %eax,0x4(%esp) cdc: 8b 45 08 mov 0x8(%ebp),%eax ; 'ctx' parameter passthru cdf: 89 04 24 mov %eax,(%esp) ce2: e8 30 fe ff ff call b17 <WCEL_InsertString> ce7: c9 leave ce8: c3 ret --- snip --- DWARF(2) symbol info: --- snip --- $ objdump -W editline.o <1><cf7>: Abbrev Number: 43 (DW_TAG_subprogram) <cf8> DW_AT_name : (indirect string, offset: 0x25b): WCEL_InsertChar <cfc> DW_AT_decl_file : 3 <cfd> DW_AT_decl_line : 327 <cff> DW_AT_prototyped : 1 <d00> DW_AT_low_pc : 0xcba <d04> DW_AT_high_pc : 0xce9 <d08> DW_AT_frame_base : 0x3b8 (location list) <d0c> DW_AT_sibling : <0xd3c> <2><d10>: Abbrev Number: 27 (DW_TAG_formal_parameter) <d11> DW_AT_name : ctx <d15> DW_AT_decl_file : 3 <d16> DW_AT_decl_line : 327 <d18> DW_AT_type : <0x847> <d1c> DW_AT_location : 2 byte block: 91 0 (DW_OP_fbreg: 0) <2><d1f>: Abbrev Number: 27 (DW_TAG_formal_parameter) <d20> DW_AT_name : c <d22> DW_AT_decl_file : 3 <d23> DW_AT_decl_line : 327 <d25> DW_AT_type : <0xf7> <d29> DW_AT_location : 2 byte block: 91 5c (DW_OP_fbreg: -36) <2><d2c>: Abbrev Number: 44 (DW_TAG_variable) <d2d> DW_AT_name : (indirect string, offset: 0x67a): buffer <d31> DW_AT_decl_file : 3 <d32> DW_AT_decl_line : 329 <d34> DW_AT_type : <0xa2a> <d38> DW_AT_location : 2 byte block: 91 6c (DW_OP_fbreg: -20) --- snip --- DW_AT_frame_base = 0x3b8 -> Location list for 0x3b8 --- snip --- $ objdump --dwarf=loc editline.o editline.o: file format elf32-i386 Contents of the .debug_loc section: ... 000003b8 00000cba 00000cbb (DW_OP_breg4 (esp): 4) 000003c4 00000cbb 00000cbd (DW_OP_breg4 (esp): 8) 000003d0 00000cbd 00000ce8 (DW_OP_breg5 (ebp): 8) 000003dc 00000ce8 00000ce9 (DW_OP_breg4 (esp): 4) 000003e8 <End of list> ... --- snip --- What might be the culprit here (see disassembly) is that 'c' is actually both: a function parameter ('DW_TAG_formal_parameter' -> 'cc0:') and a local variable ('cc3:'). The DWARF symbol info contains only one entry. Maybe that's something that confuses the debugger (function parameter handler combined with negative addressing mode which ought to apply for local variable). $ sha1sum odbg201.zip d41fe77a2801d38476f20468ab61ddce14c3abb8 odbg201.zip $ du -sh odbg201.zip 6.7M odbg201.zip $ wine --version wine-1.7.16-178-g7e874ae 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 9

[Bug 20230] New: GetThreadTimes() and the Actual and Pseudo Current Thread Handles
by wine-bugs＠winehq.org 11 Feb '21

11 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=20230 Summary: GetThreadTimes() and the Actual and Pseudo Current Thread Handles Product: Wine Version: 1.1.30 Platform: PC URL: http://rh-software.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: ray(a)pobox.co.uk Some time ago I had an issue with SIV being unable to read the thread CPU time usage when using GetThreadTimes(). I tracked down to the following and then did a work-a-round. The "Current Thread" effectively has 2 current thread handles, these are the actual thread handle and the ~0 pseudo handle as returned by GetCurrentThread(). When a call is made to GetThreadTimes() this calls NtQueryInformationThread( ThreadTimes ) which contains the test "if (handle == GetCurrentThread())". As a result of this when GetThreadTimes() is called with the actual thread handle no data is returned. \WINE-1.1.30\dlls\ntdll\thread.c(1011): if (handle == GetCurrentThread()) I suspect the code should be changed to allow both the pseudo and actual thread handles to be used as a minimum, better still would, when possible, be to implement this function for any thread. While searching the source I also noticed: NTSTATUS WINAPI NtSetInformationThread( HANDLE handle, THREADINFOCLASS class, LPCVOID data, ULONG length ) { NTSTATUS status; switch(class) { case ThreadZeroTlsCell: if (handle == GetCurrentThread()) And suspect that code would benefit from a similar fix. -- 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 18

[Bug 23431] New: provide a stub for ntdll.NtSystemDebugControl() (Ollydbg 2.x)
by wine-bugs＠winehq.org 11 Feb '21

11 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=23431 Summary: provide a stub for ntdll.NtSystemDebugControl() (Ollydbg 2.x) Product: Wine Version: 1.2-rc5 Platform: x86 URL: http://www.ollydbg.de/version2.html OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, a simple one... Ollydbg 2.x uses NtSystemDebugControl( DebugSysReadVirtual, ...) to read kernel memory (driver/OS address space) for informational purposes. Failure to do so doesn't cause harm. Although this approach doesn’t require any additional kernel driver (only the SeDebugPrivilege privilege on the running process) it's only useful for Windows XP systems. It's disallowed since Windows Vista/Windows 7. Not really useful in Wine but it obviously needs a stub. --- snip --- wine: Call from 0x7bc3d2d0 to unimplemented function ntdll.dll.NtSystemDebugControl, aborting First chance exception: unimplemented function ntdll.dll.NtSystemDebugControl called in 32-bit code (0x7bc3d2d0). ... =>0 0x7bc3d2d0 __wine_spec_unimplemented_stub+0x50(module="ntdll.dll", function="NtSystemDebugControl") [/opt/wine/wine-build/dlls/ntdll/../../../wine-git/dlls/ntdll/exception.c:268] in ntdll (0x00334434) 1 0x7bc1f895 __wine_stub_NtSystemDebugControl+0x28() in ntdll (0x00334434) 2 0x004467ae in ollydbg (+0x467ad) (0x00334460) 3 0x0044698b in ollydbg (+0x4698a) (0x00334484) --- snip --- Dump params and return STATUS_NOT_IMPLEMENTED to keep it running ;-) 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 6

[Bug 27222] New: dbghelp.dll.SymEnumSourceFilesW needed (ollydbg2)
by wine-bugs＠winehq.org 11 Feb '21

11 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=27222 Summary: dbghelp.dll.SymEnumSourceFilesW needed (ollydbg2) Product: Wine Version: 1.3.20 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: dbghelp AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, while attaching to a target using JIT (replacing winedbg), the following crash occurred: --- snip --- wine: Call from 0x7b838aa3 to unimplemented function dbghelp.dll.SymEnumSourceFilesW, aborting --- snip --- A stub keeps it from crashing (though it should not be hard to implement a wide character version). +tid,+dbghelp: --- snip --- ... fixme:dbghelp:SymEnumSourceFilesW 0x58 400000 (null) 0x4c06d8 0x400000: stub! fixme:dbghelp:SymEnumSourceFilesW 0x58 68350000 (null) 0x4c06d8 0x68350000: stub! fixme:dbghelp:SymEnumSourceFilesW 0x58 68490000 (null) 0x4c06d8 0x68490000: stub! fixme:dbghelp:SymEnumSourceFilesW 0x58 68530000 (null) 0x4c06d8 0x68530000: stub! fixme:dbghelp:SymEnumSourceFilesW 0x58 68590000 (null) 0x4c06d8 0x68590000: stub! fixme:dbghelp:SymEnumSourceFilesW 0x58 685b0000 (null) 0x4c06d8 0x685b0000: stub! fixme:dbghelp:SymEnumSourceFilesW 0x58 685f0000 (null) 0x4c06d8 0x685f0000: stub! ... --- snip --- 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 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs February 2016