wine-bugs July 2009

wine-bugs@winehq.org

1 participants
6001 discussions

[Bug 16822] New: Mass Effect: Mouse input does not work (almost completely)
by wine-bugs＠winehq.org 21 Oct '11

21 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=16822 Summary: Mass Effect: Mouse input does not work (almost completely) Product: Wine Version: 1.1.12 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: cuchac(a)email.cz Running Mass Effect the mouse is not working properly. In menu, there are no "onMouseOver" or "onMouseClick" actions - keyboard navigation works well. During gameplay the mouse clicking works well, but the mouse movement does not. It is not a problem of mouse warping, the game does not react to mouse movements at all. I have tried combination of turning on/off full-screen, virtual desktop, "allow mouse leaving" and "MouseWarpOverride". Nothing works. It looks like the mouse action (clicks) specific to some location are not working (button clicking), but mouse actions not related to some screen area works - mouse wheel zooming in map screen, select sentence during dialogs.... -- 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.

1 53

[Bug 17206] New: alt.binz 0.24.6: Minimize to systray, icon flickers, right click on systray icon, icon menu won't disappear
by wine-bugs＠winehq.org 21 Oct '11

21 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=17206 Summary: alt.binz 0.24.6: Minimize to systray, icon flickers, right click on systray icon, icon menu won't disappear Product: Wine Version: 1.1.14 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ih8junkmai1(a)hotmail.com Bug encountered on: ------------------------------------------------------------------------------------- Ubuntu 8.10 amd64 Wine 1.1.14 (wine_1.1.14~winehq0~ubuntu~8.10-0ubuntu1_amd64.deb) Application: Alt.binz 0.24.6 http://appdb.winehq.org/objectManager.php?sClass=application&iId=5214 Steps to Reproduce ------------------------------------------------------------------------------------- 1. launch alt.binz with wine. .. wine /pathtoaltbinz/altbinz.exe 2. Minimize alt.binz window .. (alt.binz is minimized to systray, alt.binz icon flickers) 3. Right click on alt.binz icon in systray .. (alt.binz menu appears) 4. Click anywhere on desktop. .. (alt.binz menu will not disappear) 5. Double click on alt.binz icon in systray .. (alt.binz icon in systray will disappear. menu remains. The only way to get the menu to disappear is to close alt.binz. -- 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.

1 7

[Bug 19370] New: Secret of Monkey Island audio functioning is dependent on Wine's sample rate
by wine-bugs＠winehq.org 21 Oct '11

21 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=19370 Summary: Secret of Monkey Island audio functioning is dependent on Wine's sample rate Product: Wine Version: 1.1.26 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dsound AssignedTo: wine-bugs(a)winehq.org ReportedBy: ehoover(a)mines.edu The Secret of Monkey Island: Special Edition's audio only works when Wine's "Default Sample Rate" is set to 44100. Other sample rates allow the game to load, but the game is completely silent. This occurs when using the alsa driver, I'm unsure whether OSS has the same issue since MI:SE will not load when the oss driver is selected. -- 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.

1 44

[Bug 10910] New: winealsa and PulseAudio
by wine-bugs＠winehq.org 21 Oct '11

21 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=10910 Summary: winealsa and PulseAudio Product: Wine Version: 0.9.51. Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-binary AssignedTo: wine-bugs(a)winehq.org ReportedBy: atari(a)gabo.pl winealsa is unable to work with PulseAudio. This is my /etc/asound.conf: pcm.pulse { type pulse } ctl.pulse { type pulse } pcm.!default { type pulse } ctl.!default { type pulse } This is registry entries for Alsa configurations: REGEDIT4 [HKEY_CURRENT_USER\Software\Wine\Alsa Driver] "AutoScanCards"="N" "AutoScanDevices"="N" "DeviceCount"="1" "DeviceCTL1"="pulse" "DevicePCM1"="pulse" "UseDirectHW"="N" And I get this error in wine log: err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element I tracked it in wine source code to file dlls/winealsa.drv/alsa.c With following comment: /* Setup and find an element id that exactly matches the characteristic we want ** FIXME: It is probably short sighted to hard code and fixate on PCM Playback Volume */ Unfortunetly I know to little about Alsa to fix it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 60

[Bug 19037] New: CTRL key automatically released?
by wine-bugs＠winehq.org 21 Oct '11

21 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=19037 Summary: CTRL key automatically released? Product: Wine Version: 1.1.24 Platform: PC OS/Version: Linux Status: NEW Keywords: download, source Severity: minor Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Fire up notepad, type some gibberish, then use "CTRL+A, CTRL+C, CTRL+F". This brings up the find menu. Now, while still holding CTRL, press CTRL+V. Instead of pasting, you'll just get 'v'. Let go of CTRL and press CTRL+V. You'll get your gibberish pasted. Very annoying, now that I'm using Notepad++ as my regular (dogfood) text editor. -- 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.

1 7

[Bug 11728] New: Picasa / Facebook Uploader does not work
by wine-bugs＠winehq.org 19 Oct '11

19 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=11728 Summary: Picasa / Facebook Uploader does not work Product: Wine Version: 0.9.56. Platform: PC URL: http://apps.facebook.com/picasauploader/ OS/Version: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thestig(a)google.com Prerequisite: a facebook account Steps to reproduce: 1. Install Picasa from http://picasa.google.com/ 2. Install wine gecko 3. Install the facebook uploader from http://apps.facebook.com/picasauploader/ as follows: wine 'c:\Program Files\Picasa2\Picasa2.exe' picasa://importbutton/?url=http://www.webkinesis.com/fbpicasa/facebook.pbf 4. Start Picasa, select some pictures and try to upload using the facebook button Expected Results: Picasa creates an album, uploads the pictures to facebook. (tested on WinXP) Actual Results: Picasa creates an album, but nothing gets uploaded. -- 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.

1 8

[Bug 17718] New: Fatal error 'Cannot allocate red zone for initial thread' on FreeBSD
by wine-bugs＠winehq.org 17 Oct '11

17 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=17718 Summary: Fatal error 'Cannot allocate red zone for initial thread' on FreeBSD Product: Wine Version: 1.1.17 Platform: PC OS/Version: FreeBSD Status: NEW Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gerald(a)pfeifer.com CC: tijl(a)ulyssis.org, austinenglish(a)gmail.com Wine 1.1.17 causes the following on FreeBSD 7.2 when starting almost any application (this is for an old version of calc.exe): Fatal error 'Cannot allocate red zone for initial thread' at line 384 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 2) err:module:attach_process_dlls "ntdll.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\\windows\\system32\\wineboot.exe" failed, status 80000101 err:process:__wine_kernel_init boot event wait timed out Fatal error 'Cannot allocate red zone for initial thread' at line 384 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 2) err:module:attach_process_dlls "ntdll.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"Z:\\home\\pfeifer\\_\\wcalc.exe" failed, status 80000101 Segmentation fault (core dumped) -- 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.

1 10

[Bug 12267] New: winstone 32 hangs
by wine-bugs＠winehq.org 17 Oct '11

17 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=12267 Summary: winstone 32 hangs Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Here's what happens when you launch c:\zdbench\ws32\ui.exe: it puts up its window, says "examining the execution environment" (although you can't see it, since the window is too big, and falls off the bottom), and hangs. err:ntdll:RtlpWaitForCriticalSection section 0x7b922ee0 "syslevel.c: Win16Mutex" wait timed out in thread 0016, blocked by 0012, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x7bc8d6e4 "loader.c: loader_section" wait timed out in thread 0012, blocked by 0016, retrying (60 sec) It hangs just like this on XP, too. But what the heck, if we could get it to not hang on wine, that'd be nice. -- 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.

1 6

[Bug 11109] New: dream of mirror online crash
by wine-bugs＠winehq.org 17 Oct '11

17 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=11109 Summary: dream of mirror online crash Product: Wine Version: 0.9.52. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: petifrancais(a)gmail.com Created an attachment (id=10143) --> (http://bugs.winehq.org/attachment.cgi?id=10143) txt contenant les erreurs en console The game game domo crash after the logo "GameTribe" -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 11

[Bug 16674] New: Battle for middle earth2: No network multiplayer possible
by wine-bugs＠winehq.org 17 Oct '11

17 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=16674 Summary: Battle for middle earth2: No network multiplayer possible Product: Wine Version: 1.1.11 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P4 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mcflow-forum(a)gmx.net Multiplayer games with Battle for Middle Earth2 in wine are not possible. According to the information on the game package it uses TCP/IP for network multiplayer. I already tried using the native dplay dlls like it is stated in the wiki, LAN still does not work. It happens like this: I enter the network mode and the game displays myself two times in the players list. The other player sees me in the list only one time, as it should be. I can read what he writes and vice versa. If I write something I can see it two times in the chat. For the other user it appears only one time. Now, if I open a game, the other player can see it in the game list. If he wants to join he gets a "Connection Timout" error. Same happens if the other player opens a game and I want to join it. I searched the Bugzilla for quite a time now because I do not want to open a duplicate bug. I found a few things that first sounded interesting but when I tested them nothing changed. I found a note at the AppDB page of Garena 3.0 (http://appdb.winehq.org/objectManager.php?sClass=version&iId=14147&iTesting…) Patching with the patch that is linked there did not solve the problem with wine-1.1.11(well one of the hunks failed but it compiled) In Bug 9787 there also was a patch for the AcceptEX for wine-1.1.6. It did not work with wine-1.1.6. It said that wine does not include AcceptEX. I'm not sure if "The battle for middle earth" requires it. I did not find anything about it on the net except that it uses tcp/ip. -- 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.

1 27

[Bug 19083] New: Respondus LockDown Browser: outside processes should not be able to detect its window (appinstall)
by wine-bugs＠winehq.org 17 Oct '11

17 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=19083 Summary: Respondus LockDown Browser: outside processes should not be able to detect its window (appinstall) Product: Wine Version: 1.1.21 Platform: PC URL: https://hdc.tamu.edu/files/book/6/425/LockDownSetup_1. 0.3.exe OS/Version: Linux Status: NEW Keywords: download, testcase Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Not sure how to describe this exactly...but the Respondus Lockdown Browser is meant to be used by universities to make sure that students don't use other programs when taking quizzes/exams/etc. As a result, it does some really funky stuff...While writing an appinstall test for it, found a few interesting things. First up, on windows, the IfWinExist (http://www.autohotkey.com/docs/commands/IfWinExist.htm) function fails for this window (never seen that happen for any other app). On wine, however, we detect it just fine. -- 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.

1 4

[Bug 15250] New: MINITAB 14 graph editor crashes when File menu is clicked
by wine-bugs＠winehq.org 17 Oct '11

17 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=15250 Summary: MINITAB 14 graph editor crashes when File menu is clicked Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: nodisgod(a)yahoo.com Created an attachment (id=16034) --> (http://bugs.winehq.org/attachment.cgi?id=16034) rzipped relay log With current Git (wine-1.1.4-292-g4b4109a), when clicking on the File menu in the graph editor, mtb14ge.exe, the application crashes. The point at which the application crashes seems to be here: 0009:Call user32.CallWindowProcW(7edae5b0,00010030,00000229,00000000,00000000) ret=5f8487d1 0009:Call window proc 0x7edae5b0 (hwnd=0x10030,msg=WM_MDIGETACTIVE,wp=00000000,lp=00000000) 0009:Ret window proc 0x7edae5b0 (hwnd=0x10030,msg=WM_MDIGETACTIVE,wp=00000000,lp=00000000) retval=00000000 0009:Ret user32.CallWindowProcW() retval=00000000 ret=5f8487d1 0009:Ret window proc 0x5f870878 (hwnd=0x10030,msg=WM_MDIGETACTIVE,wp=00000000,lp=00000000) retval=00000000 0009:Ret user32.SendMessageW() retval=00000000 ret=5f862aa3 0009:Call KERNEL32.TlsGetValue(00000003) ret=5f870ec6 0009:Ret KERNEL32.TlsGetValue() retval=00139408 ret=5f870ec6 0009:Call KERNEL32.TlsGetValue(00000003) ret=5f870ec6 0009:Ret KERNEL32.TlsGetValue() retval=00139408 ret=5f870ec6 0009:Call KERNEL32.TlsGetValue(00000003) ret=5f870ec6 0009:Ret KERNEL32.TlsGetValue() retval=00139408 ret=5f870ec6 trace:seh:raise_exception code=c0000005 flags=0 addr=0x32eeda Compressed relay log is attached. -- 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.

1 11

[Bug 11077] New: does not find a serial port while running this application under wine
by wine-bugs＠winehq.org 17 Oct '11

17 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=11077 Summary: does not find a serial port while running this application under wine Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: only4john(a)gmail.com Environment: wine under Ubuntu 7.10 Hardware Device: IRISYS 1001 thermal imager (http://www.entherm.com/Irisys/IRISYS%20Thermal%20Imager.htm) Driving Application: http://only4john.googlepages.com/Imager3309.exe The Driving Application can not find serial port while running the application under wine, while the PC has a serial port. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 13

[Bug 14847] New: UFO Extraterrestials: Problems with mouse cursor and textures.
by wine-bugs＠winehq.org 15 Oct '11

15 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=14847 Summary: UFO Extraterrestials: Problems with mouse cursor and textures. Product: Wine Version: 1.0.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: RodionKarimov(a)yandex.ru Problem with mouse: cursor is shown not exactly there where it is, for exmple, when cursor is graphically shown a long away from button - the button is selected, when it is on button - button is not selected. There is some problem in inner game mouse driver, because, when i am changing mouse sensitivity in file "ufo-et.ini", that is located in "data" directory from 255 to 100, image of mouse cursor starts to be much closer to there, where it actually is. But not exactly. And some times image of cursor again starts to go far from exact cursor location, for example: sometimes when rotating the globe or in tactical mode, when shooting. Problem with textures: when in "ufo-et.ini" "scissortesting=true", that default is, there is not seen in global mode: images of soldiers; research tasks; rifles, pistols, grenades and ammunition of soldiers; and name of the save game that is being enter when saving game. When "scissortesting=false" all of that is shown, but name of the saving game is very little, project names is also very little, images of soldioers and weapons is also very little. And everything of this is not on its place, for example images of weapons is right and down from its location; images of soldiers are placed down from its locations; names of projects are right and down from its location, but they are selecting and activating by mouse at that position where they must be. -- 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.

1 27

[Bug 17536] New: Atari Scrabble Online fails to install (regression)
by wine-bugs＠winehq.org 15 Oct '11

15 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=17536 Summary: Atari Scrabble Online fails to install (regression) Product: Wine Version: 1.1.11 Platform: PC URL: http://appdb.winehq.org/objectManager.php?sClass=version &iId=12955 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Created an attachment (id=19670) --> (http://bugs.winehq.org/attachment.cgi?id=19670) Wine 1.1.15 +msi Atari Scrabble Online fails to install. The culprit seems to be: err:msi:ITERATE_Actions Execution halted, action L"DX9_Launcher.A545835B_7768_4D96_A5BC_930949616C2D" returned 1603 At this point the installer attempts to start the DirectX9 installer, whether it is already installed or not. There therefore is no workaround. Tested in Wine 1.1.11 and 1.1.15 and bug exists. Tested in Wine 1.0 and bug does not exist. Result of bisect: 731306bf78f2b8a6a92448e1977268b4396eb449 is first bad commit commit 731306bf78f2b8a6a92448e1977268b4396eb449 Author: James Hawkins <jhawkins(a)codeweavers.com> Date: Tue Sep 2 01:01:59 2008 -0500 kernel32: Fix two tests that fail in win2k3 and modify LoadLibraryEx to match this behavior. :040000 040000 64ed6c6c7ae8c6e131079052e9113f07a467d58b 64a781d6056ae364ba95c128901381cc6343c06a M dlls which doesn't make much sense to me. -- 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.

1 22

[Bug 11419] New: Installation of Intel Indeo Video freezes
by wine-bugs＠winehq.org 15 Oct '11

15 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=11419 Summary: Installation of Intel Indeo Video freezes Product: Wine Version: 0.9.54. Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: elicoten(a)live.co.uk Installation gets upto "searching for components: Netscape", and about 9% on the progress bar then freezes. Cannot be installed. -- 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.

1 9

[Bug 11239] New: Steam Games No Longer Start - bisected the cause to ntdll
by wine-bugs＠winehq.org 13 Oct '11

13 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=11239 Summary: Steam Games No Longer Start - bisected the cause to ntdll Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: philcostin(a)hotmail.com The following patch, introduced on Jan 15th 2008 has resulted in Steam games being unable to start. bd352bcd1c98ed91bdb337e73cddfd8ceac095d6 err:seh:setup_exception nested exception on signal stack in thread 004f eip 7efc20b3 esp 7ffdb770 stack 0x241000-0x350000 -- 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.

1 20

[Bug 14390] New: Gmax 1.2: Fatal Error on Install - Ended Prematurely.
by wine-bugs＠winehq.org 13 Oct '11

13 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=14390 Summary: Gmax 1.2: Fatal Error on Install - Ended Prematurely. Product: Wine Version: 1.1.0 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P1 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gaming4jc2(a)yahoo.com Created an attachment (id=14701) --> (http://bugs.winehq.org/attachment.cgi?id=14701) Fatal Error on install. When installing GMAX 1.2 on WINE 1.1.0 I receive the following errors which are attached. -- 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.

1 15

[Bug 18777] New: Wine 1.1.22+ resets customized FontLink when switching locales
by wine-bugs＠winehq.org 12 Oct '11

12 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=18777 Summary: Wine 1.1.22+ resets customized FontLink when switching locales Product: Wine Version: 1.1.22 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: matthewsage(a)live.com CC: Paul.Hampson(a)Pobox.com Created an attachment (id=21546) --> (http://bugs.winehq.org/attachment.cgi?id=21546) Regression test that shows the patch that broke the desired functionality Whenever you switch locales (using the latest Wine dev. version -1.1.22-), whatever custom Font Linking you have made in the FontLink/SystemLink register key will be wiped out. This was tested on Wine 1.1.22, after wiping out ~/.wine I tested it with the Ubuntu x86_64 binary package from the budgetdedicated servers, AND after building from source. Steps to reproduce: 1) Run "regedit" 2) Set some System Font Linking replacements in the HKLM/Software/Microsoft/Windows NT/CurrentVersion/FontLink/SystemLink register key (in my case: Tahoma -> VL Gothic, Microsoft Sans Serif -> VLGothic, MS Sans Serif -> VL Gothic) 3) Run any Win32 application with LANG set to a different locale (in my case, LANG=ja_JP.UTF-8) Expected results: The application is executed, whatever Font Linking you made is visible (which means that the custom Font Linking I made is respected by Wine). Actual Results: The application is executed, whatever Font Linking you made is not visible. If you run "regedit" again, you'll see that the FontLink/SystemLink key is now empty. Workaround: Always run Wine apps with the same locale (LANG=ja_JP.UTF-8 in my case) - That would include regedit itself, so that the Font Linking you set up is not wiped as soon as you run another app with a different locale. -- 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.

1 11

[Bug 10273] New: satisfy SafeDisc 2.x heuristic API analyzer by "adjusting" API exports/entry statistics of wine builtins
by wine-bugs＠winehq.org 12 Oct '11

12 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=10273 Summary: satisfy SafeDisc 2.x heuristic API analyzer by "adjusting" API exports/entry statistics of wine builtins Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-kernel AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=8924) --> (http://bugs.winehq.org/attachment.cgi?id=8924) Patch which should fix SafeDisc 2.x copy protection api analyzer issue Hello, if not interested in technical details goto (2) ;-) I made this a separate bug report like http://bugs.winehq.org/show_bug.cgi?id=9925 (SafeDisc 1.x stopper) because SafeDisc has many flavors that differ in various technical ways and can't be discussed/handled in a single SafeDisc "metabug" like http://bugs.winehq.org/show_bug.cgi?id=219 SafeDisc Major version based separation allows better tracking of "completion" state (1.x/2.x/3.x/4.x). ----------- (1) It took me a couple of days to get an idea what SafeDisc 2.x really does with the API exports and to find a way to cope with it... Various anti-debugging techniques and nasty runtime code obfuscation made this journey somewhat challenging. Parts of SafeDisc 2.x analyze the API code of the following system libraries: kernel32.dll (wine builtin) user32.dll (wine builtin) gdi32.dll (wine builtin) cdasdtst.dll (developer backdoor?) The latter one is probably a "developer backdoor", used to verify their code/algorithms (not needed to be present). For each of these libraries all named exports are taken into account. A number of API entry opcode sequences are read and used for statistical analysis (number depends on type of encountered opcodes). >From what I've seen there is some kind of "behavioural probability" of each API entry calculated, with typical opcode sequences having a "weighting". Just think of advanced heuristic detection methods of antivirus scanners and you get the idea ;-). Anyway, wine's builtin libraries differ in their signatures from windows entry code and to make things worse, wine's +relay/+snoop feature heavily interferes with the analyzer results. :-( First I made some experiments with additional (dummy) function exports, small __asm__ wrappers with opcode sequences to see how the distribution of opcodes influences the analyzer results. The result was rather disappointing. I needed a large number of exports to gain some results but not significantly enough to get below the "bad" threshold. Then I came across the magic "0" value. As soon as I used this value either as first .byte on API entry or init value for data export, the entry scan was short circuited. This value seemed to have the highest influence of all code/data sequences used. I added quite a number of data exports - aliased to initialized "0" value - safe enough to let even wine's +relay work (remember: relay code influences analyzer). If you look at the patch don't get mad ;-) You will see a crapload of named "__wine_safedisc2" data exports/aliases added to wine builtin kernel32, user32 and gdi32. For the record: http://bugs.winehq.org/show_bug.cgi?id=9926 which talks about "problematic" gdi32 data exports (pfnPalette stuff) in SafeDisc 3.x. SafeDisc 2.x code triggers SEH upon exported function pointers too but this is gracefully handled. No harm at all. I wonder if this is really a problem in SafeDisc 3.x ... I thought about other possible solutions but found no one easier to implement to prove my findings without hurting wine too much :-) Making wrappers of the whole kernel32, user32, gdi32 named exports API just to please the entry analyzer is not an option to me. Another way could be the relocation of export table upon module loading, expanding it at runtime by adding the required number of "statistics fakers" (data exports with zero init). This requires modifying the ntdll loader .. though i'm not sure if this approach breaks other applications/braindamaged PE protection stuff which expect certain conditions to be met (tables present at specific sections/memory areas). ------------------------------ (2) Well, take it as proof of concept. Play with it. I tested my patch with a few SafeDisc 2.x games I have original media. No cracks/no-cd patches were used. Only official game patches were used. Battlefield 1924 (1.6x) - SafeDisc 2.6/2.8 Road To Rome (BF1942 expansion) - SafeDisc 2.8 Battlefield Vietnam - SafeDisc 2.9 All of these work fine for me with the patch applied. Please test this patch on many SafeDisc 2.x games as possible and report your results (works or works not). Make sure you have original media mounted and drive/data is visible within wine. If it fails for first time, the media might not ready yet, try again then (I experienced this sometimes). Use this link to verify what SafeDisc Version is used: http://www.120search.net/ (alcohol software copy protection database) Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 48

[Bug 9798] New: bioshock demo needs glsl enabled
by wine-bugs＠winehq.org 12 Oct '11

12 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=9798 Summary: bioshock demo needs glsl enabled Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=8240) --> (http://bugs.winehq.org/attachment.cgi?id=8240) crash log with glsl disabled Hello, Bioshock demo crashes if glsl is not enabled. Attached are relevant traces made with: WINEDEBUG=+seh,+tid,+d3d,+d3d_shader wine ./Bioshock.exe -dx9 Using following registry settings enables bioshock demo to run: --- snip --- HKEY_CURRENT_USER/Software/Wine/Direct3D UseGLSL = "enabled" --- snip --- Optional: OffscreenRenderingMode = "fbo" ================== Addendum: wine --version wine-0.9.45-406-g2ba3247 Currently uses secuROM hack (http://bugs.winehq.org/attachment.cgi?id=8235 ) to run, see http://bugs.winehq.org/show_bug.cgi?id=7065 Be sure to include "-dx9" command line to work around directx 10 issue. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 6

[Bug 10225] New: SafeDisc 2. x triggers async device ioctl status code propagation bug in wine server
by wine-bugs＠winehq.org 12 Oct '11

12 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=10225 Summary: SafeDisc 2.x triggers async device ioctl status code propagation bug in wine server 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=8843) --> (http://bugs.winehq.org/attachment.cgi?id=8843) relevant trace which shows ioctl status code propagation bug Hello, while testing my proof-of-concept patch which makes SafeDisc v2 (yuck!) finally work, I stumbled across a nasty ioctl status code propagation (completion) bug in wine server. Wasted several hours on it .. I was suspecting SD issue whole time, but its a wine server bug :( Attached is relevant trace (WINEDEBUG=+seh,+tid,+relay,+ntoskrnl,+server wine ./BfVietnam.exe) Before the bug is triggered, the SafeDisc security driver makes several device ioctl requests which return 0xC0000001 (unsuccessful) on purpose, e.g. reading debug Drx registers with index that does not exist. This is intended to fool reversers :-) The next operation - checking IDT entries should succeed - but does not (as seen from calling client). The kernel driver completes the operation successfully and returns irp.IoStatus.u.Status == 0 with xxxx bytes in output buffer. I verified it several times by debugging the kernel driver. Upon driver ioctl call return, get_next_device_request() is triggered again in ntoskrnl event loop which sets the return data (and status code) -> set_ioctl_result(). This queues an APC, waking up the client (alertable state). The client process device ioctl completes with 0 (FALSE) which is wrong. Further debugging showed that ioctl_completion APC (dlls/ntdll/file.c) returns the errornous status code in get_ioctl_result() when woken up by server. This error is then propagated in server_ioctl_file() to result in wrong NtDeviceIoControlFile() return code. What puzzled me is that "ioctl->status" is correctly set by set_ioctl_result() (=0) but get_ioctl_result() - called within client context - yields the previous error code (0xC0000001 of failed request). This is either a problem of global vs. thread local error status (global_error vs. current->error/thread) or the ioctl call data is the wrong one. The following patch works for me, letting SD 2.x continue - though i'm not sure if it's right: --- snip --- diff --git a/server/device.c b/server/device.c index 46b2796..8fe8f7c 100644 --- a/server/device.c +++ b/server/device.c @@ -528,7 +528,7 @@ DECL_HANDLER(get_ioctl_result) ioctl->out_data = NULL; } } - set_error( ioctl->status ); + list_remove( &ioctl->dev_entry ); release_object( ioctl ); /* no longer on the device queue */ } --- snip --- Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 8

[Bug 10293] New: sequentially running games/ apps with different SafeDisc versions fails
by wine-bugs＠winehq.org 12 Oct '11

12 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=10293 Summary: sequentially running games/apps with different SafeDisc versions fails Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-kernel AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=8945) --> (http://bugs.winehq.org/attachment.cgi?id=8945) Patch which fixes various isses regarding kmode driver unload/reload Hello, currently wine's kernel mode driver cleanup/unloading facility has several issues when it comes to applications/games that unload and reload different driver versions on the fly. Example: run multiple SafeDisc 2.x, 3.x and 4.x games sequentially. Symptoms: game either hangs/crashes/exits silently Usually the SD security driver is placed in "c:\windows\system32\drivers\secdrv.sys" If a SafeDisc protected program encounters a driver version that is incompatible it does the following: - stop the current security service (should unload the driver) - unpack own security driver from resources to temp storage and move the binary to "c:\windows\system32\drivers\secdrv.sys", overwriting the previous - restart the service (loads the new driver) This currently fails for various reasons: (1) The driver binary is loaded using LoadLibrary() -> the matching FreeLibrary() is missing on service stop. This leads to sharing violation when the driver binary going to be replaced (CopyFile fails). (2) No driver unload routine called. Very problematic. Various objects (symlinks) created by driver entry are not freed. When the driver is reloaded the init routine usually fails with "object exists". (3) Driver state objects (driver_obj, driver_extension) have undefined state due to static storage. Raises all sorts of problems because the driver entry routine does not init all fields. --------- Attached is a patch which fixes these problems, allowing to sequentially run programs with different SafeDisc Versions. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 10

[Bug 10451] New: Various AutoDesk 2008 product installers fail due to unimplemented msi. MsiEnumComponentCostsW
by wine-bugs＠winehq.org 12 Oct '11

12 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=10451 Summary: Various AutoDesk 2008 product installers fail due to unimplemented msi.MsiEnumComponentCostsW Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=9156) --> (http://bugs.winehq.org/attachment.cgi?id=9156) stub impl of msi.MsiEnumComponentCostsW to keep AutoDesk 2008 installers happy Hello, various AutoDesk 2008 product installers fail due to unimplemented msi.MsiEnumComponentCostsW API (mentioned in bug 9809). --- snip --- wine: Call from 0x7b841460 to unimplemented function msi.dll.MsiEnumComponentCostsW, aborting wine: Unimplemented function msi.dll.MsiEnumComponentCostsW called at address 0x7b841460 (thread 000e), starting debugger... Unhandled exception: unimplemented function msi.dll.MsiEnumComponentCostsW called in 32-bit code (0x7b8414d8). --- snip --- Attached patch makes installer happy. Though that API (A/W) should be fleshed out some day ... this is left as exercise for msi maintainers :-) If you test this on AutoDesk 2008 installers, you need my shell32/shlfileop patch from bug 9809 too. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 6

[Bug 10478] New: wine server get/set thread context doesn' t work correctly if simultaneously used by debugger and debuggee
by wine-bugs＠winehq.org 12 Oct '11

12 Oct '11

http://bugs.winehq.org/show_bug.cgi?id=10478 Summary: wine server get/set thread context doesn't work correctly if simultaneously used by debugger and debuggee Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-debug AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=9209) --> (http://bugs.winehq.org/attachment.cgi?id=9209) WINEDEBUG=+tid,+server,+win trace of debugging session Hello, while debugging a target with some debugger I experienced severe problems with wine server get/set thread context implementation. It doesn't work correctly if the get/set thread context API is simultaneously used by both, the debugger and the debuggee to manage exception events/control execution transfer. Attached is WINEDEBUG=+tid,+seh,+win trace (don't bother with +win channel output, was for my own purpose). pid=0008, tid=0009 debugger main thread pid=0008, tid=000d debugger debug event loop thread pid=000e, tid=000f debuggee main thread pid=000e, tid=0010 debuggee child thread pid=000e, tid=0011 debuggee child thread pid=000e, tid=0012 debuggee child thread Search for "000d: get_thread_context() = ACCESS_DENIED { self=0, context={} }" in attached log and walk your way back... --- snip --- 000f: queue_exception_event( first=1, record={context={flags=00010007,eax=7b82c455,ebx=7b8ad1e4,ecx=00000000,edx=00004000,esi=00004000,edi=00197430,ebp=0034e5d4,eip=7b841378,esp=0034e570,eflags=00200216,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=a3f67070,dr1=0012e150,dr2=0034eec0,dr3=00000000,dr6=00000006,dr7=00000200,float={00000003,0034e234,33746e49,00000032,00000000,000000f8,0034e280,0034e268,00087510,00198af0,00110014,00000001,00000318,00000000,4d430002,4d430000,00198e18,00000010,00000000,00000000,00000000,4d430003,00000000,00000000,00000000,00000000,00000000,00000000}},rec={code=e06d7363,flags=1,rec=(nil),addr=0x7b841300,params={19930520,34e670,79f9acc4}} ) 000d: *wakeup* signaled=0 cookie=0x616e24c0 0010: *sent signal* signal=10 0011: *sent signal* signal=10 0012: *sent signal* signal=10 000f: queue_exception_event() = 0 { handle=0x244 } --- snip --- Debuggee main thread throws first chance C++ exception (queues event). Ok. --- snip --- 0010: set_thread_context( handle=0xfffffffe, flags=00010007, suspend=1, context={flags=0001001f,eax=00000003,ebx=0000001f,ecx=613516a4,edx=00000008,esi=613516a4,edi=7ffd4000,ebp=613516b8,eip=600007f0,esp=61351670,eflags=00200293,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={ffff037f,ffff4000,ffffffff,604b434d,035f0073,0034dc34,0000007b,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,3fff8000,00000000,80000000,00003ffe,00000000,3ffe8000,00000000,80000000,00003ffe,00000000,40038000,00004000}} ) 0010: set_thread_context() = 0 { self=1 } 0011: set_thread_context( handle=0xfffffffe, flags=00010007, suspend=1, context={flags=0001001f,eax=00000003,ebx=00000023,ecx=614624a0,edx=00000008,esi=614624a0,edi=7ffd0000,ebp=614624b4,eip=600007f0,esp=6146246c,eflags=00200293,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={ffff037f,ffff0100,ffffffff,79e7a66b,06d90073,00000000,0000007b,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,3fff8000,00000000,80000000,00003ffe,00000000,3ffe8000,00000000,80000000,00003ffd,80000000,40078662,00000100}} ) 0011: set_thread_context() = 0 { self=1 } 0012: set_thread_context( handle=0xfffffffe, flags=00010007, suspend=1, context={flags=0001001f,eax=00000003,ebx=0000003a,ecx=6c101d70,edx=00000008,esi=6c101d70,edi=7ffcc000,ebp=6c101d84,eip=600007f0,esp=6c101d3c,eflags=00200293,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={ffff037f,ffff0120,ffffffff,79e7a66b,06d90073,00000000,0000007b,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,3fff8000,00000000,80000000,00003ffe,00000000,00000000,00000000,80000000,00003ffd,60000000,400785bc,00000120}} ) 0012: set_thread_context() = 0 { self=1 } --- snip --- The debuggee child threads get SIGUSR1, suspend themselves (on purpose!). Ok. --- snip --- 000d: wait_debug_event( get_handle=1 ) 000d: wait_debug_event() = 0 { pid=000e, tid=000f, wait=(nil), event={exception,{code=e06d7363,flags=1,rec=(nil),addr=0x7b841300,params={19930520,34e670,79f9acc4},first=1} } .. 000d: continue_debug_event( pid=000e, tid=000f, status=-2147418111 ) 000f: *wakeup* signaled=0 cookie=0x34dfd4 0010: *wakeup* signaled=258 cookie=0x7ffd77b4 0011: *wakeup* signaled=258 cookie=0x7ffd37b4 000d: continue_debug_event() = 0 .. --- snip --- Debugger wakes up and sees first chance C++ exception, decides to pass it to debuggee (resumes execution of threads). Ok. --- snip --- 000f: get_exception_status( handle=0x244 ) 000f: get_exception_status() = 80010001 { context={flags=00010007,eax=7b82c455,ebx=7b8ad1e4,ecx=00000000,edx=00004000,esi=00004000,edi=00197430,ebp=0034e5d4,eip=7b841378,esp=0034e570,eflags=00200216,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=a3f67070,dr1=0012e150,dr2=0034eec0,dr3=00000000,dr6=00000006,dr7=00000200,float={00000003,0034e234,33746e49,00000032,00000000,000000f8,0034e280,0034e268,00087510,00198af0,00110014,00000001,00000318,00000000,4d430002,4d430000,00198e18,00000010,00000000,00000000,00000000,4d430003,00000000,00000000,00000000,00000000,00000000,00000000}} } 0010: get_thread_context( handle=0xfffffffe, flags=00010007, suspend=1 ) 0010: get_thread_context() = 0 { self=1, context={flags=0001001f,eax=00000003,ebx=0000001f,ecx=613516a4,edx=00000008,esi=613516a4,edi=7ffd4000,ebp=613516b8,eip=600007f0,esp=61351670,eflags=00200293,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={ffff037f,ffff4000,ffffffff,604b434d,035f0073,0034dc34,0000007b,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,3fff8000,00000000,80000000,00003ffe,00000000,3ffe8000,00000000,80000000,00003ffe,00000000,40038000,00004000}} } 0011: get_thread_context( handle=0xfffffffe, flags=00010007, suspend=1 ) 0011: get_thread_context() = 0 { self=1, context={flags=0001001f,eax=00000003,ebx=00000023,ecx=614624a0,edx=00000008,esi=614624a0,edi=7ffd0000,ebp=614624b4,eip=600007f0,esp=6146246c,eflags=00200293,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={ffff037f,ffff0100,ffffffff,79e7a66b,06d90073,00000000,0000007b,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,3fff8000,00000000,80000000,00003ffe,00000000,3ffe8000,00000000,80000000,00003ffd,80000000,40078662,00000100}} } 000d: select( flags=4, cookie=0x616e24c0, signal=(nil), prev_apc=(nil), timeout=+1.0000000, result={}, handles={0xa8} ) 000d: select() = PENDING { apc_handle=(nil), timeout=1c828ffa61af642 (+1.0000000), call={APC_NONE} } 0012: get_thread_context( handle=0xfffffffe, flags=00010007, suspend=1 ) 0012: get_thread_context() = 0 { self=1, context={flags=0001001f,eax=00000003,ebx=0000003a,ecx=6c101d70,edx=00000008,esi=6c101d70,edi=7ffcc000,ebp=6c101d84,eip=600007f0,esp=6c101d3c,eflags=00200293,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={ffff037f,ffff0120,ffffffff,79e7a66b,06d90073,00000000,0000007b,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,3fff8000,00000000,80000000,00003ffe,00000000,00000000,00000000,80000000,00003ffd,60000000,400785bc,00000120}} } 000f: get_process_info( handle=0xffffffff ) 000f: get_process_info() = 0 { pid=000e, ppid=0008, exit_code=259, priority=2, affinity=1, peb=0x7ffdf000, start_time=1c828ff9f2037c6 (-10.7374150), end_time=0 } 000f: queue_exception_event( first=1, record={context={flags=00010007,eax=7b82c455,ebx=7b8ad1e4,ecx=00000000,edx=0034ee58,esi=0034ee58,edi=e0434f4d,ebp=0034ee20,eip=7b841378,esp=0034edbc,eflags=00200212,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=02d410d8,dr2=a3f67060,dr3=00000000,dr6=00110000,dr7=00000002,float={0034eaa4,00001302,00198d10,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001,0034eadc,79e783ca,00110000,00000000,79e783e6,a3f67cf4,00000001,00197430,00000000,00000008,00000000,0034eb14,7a3296dc,ffffffff,79e783e6,79e7839d,00110000}},rec={code=e0434f4d,flags=1,rec=(nil),addr=0x7b841300,params={80004002}} ) --- snip --- Main debuggee thread SEH evaluates first chance exception and converts it internally to CLR exception, throwing again. --- snip --- 0010: set_thread_context( handle=0xfffffffe, flags=00010007, suspend=1, context={flags=0001001f,eax=00000003,ebx=0000001f,ecx=613516a4,edx=00000008,esi=613516a4,edi=7ffd4000,ebp=613516b8,eip=600007f0,esp=61351670,eflags=00200293,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={ffff037f,ffff4000,ffffffff,604b434d,035f0073,0034dc34,0000007b,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,3fff8000,00000000,80000000,00003ffe,00000000,3ffe8000,00000000,80000000,00003ffe,00000000,40038000,00004000}} ) 0010: set_thread_context() = 0 { self=1 } 0011: set_thread_context( handle=0xfffffffe, flags=00010007, suspend=1, context={flags=0001001f,eax=00000003,ebx=00000023,ecx=614624a0,edx=00000008,esi=614624a0,edi=7ffd0000,ebp=614624b4,eip=600007f0,esp=6146246c,eflags=00200293,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={ffff037f,ffff0100,ffffffff,79e7a66b,06d90073,00000000,0000007b,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,3fff8000,00000000,80000000,00003ffe,00000000,3ffe8000,00000000,80000000,00003ffd,80000000,40078662,00000100}} ) 0011: set_thread_context() = 0 { self=1 } 0012: set_thread_context( handle=0xfffffffe, flags=00010007, suspend=1, context={flags=0001001f,eax=00000003,ebx=0000003a,ecx=6c101d70,edx=00000008,esi=6c101d70,edi=7ffcc000,ebp=6c101d84,eip=600007f0,esp=6c101d3c,eflags=00200293,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={ffff037f,ffff0120,ffffffff,79e7a66b,06d90073,00000000,0000007b,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,3fff8000,00000000,80000000,00003ffe,00000000,00000000,00000000,80000000,00003ffd,60000000,400785bc,00000120}} ) 0012: set_thread_context() = 0 { self=1 } --- snip --- The debuggee child threads get SIGUSR1, suspend themselves again (on purpose!). Ok. --- snip --- 000d: suspend_thread( handle=0xd4 ) 000d: suspend_thread() = 0 { count=0 } 000d: suspend_thread( handle=0xd8 ) 000d: suspend_thread() = 0 { count=0 } 000d: suspend_thread( handle=0xf8 ) 000d: suspend_thread() = 0 { count=0 } 000d: get_thread_context( handle=0xbc, flags=0001003f, suspend=0 ) 000f: *signal* signal=19 000d: get_thread_context() = 0 { self=0, context={flags=0001003f,eax=7b82c455,ebx=7b8ad1e4,ecx=00000000,edx=0034ee58,esi=0034ee58,edi=e0434f4d,ebp=0034ee20,eip=7b841378,esp=0034edbc,eflags=00200212,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={0034eaa4,00001302,00198d10,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001,0034eadc,79e783ca,00110000,00000000,79e783e6,a3f67cf4,00000001,00197430,00000000,00000008,00000000,0034eb14,7a3296dc,ffffffff,79e783e6,79e7839d,00110000}} } 000d: read_process_memory( handle=0xb8, addr=0x7b841378 ) 000f: *signal* signal=19 000d: read_process_memory() = 0 { data={8b} } 000d: resume_thread( handle=0xbc ) 000d: resume_thread() = 0 { count=1 } 000d: resume_thread( handle=0xd4 ) 000d: resume_thread() = 0 { count=1 } 000d: resume_thread( handle=0xd8 ) 000d: resume_thread() = 0 { count=1 } 000d: resume_thread( handle=0xf8 ) 000d: resume_thread() = 0 { count=1 } 000d: continue_debug_event( pid=000e, tid=000f, status=-2147418111 ) 000f: *wakeup* signaled=0 cookie=0x34e824 0010: *wakeup* signaled=258 cookie=0x7ffd77b4 0011: *wakeup* signaled=258 cookie=0x7ffd37b4 0012: *wakeup* signaled=258 cookie=0x7ffcf7b4 000d: continue_debug_event() = 0 --- snip --- Debugger wakes up again, now seeing the CLR exception. Debugger suspends debuggee threads - although unnecessary due to debugging event before = already suspended. This exception type is unhandled, main debuggee thread receives SIGSTOP. Execution of debuggee threads resumed. --- snip --- 000f: get_exception_status( handle=0x244 ) 000f: get_exception_status() = 80010001 { context={flags=00010007,eax=7b82c455,ebx=7b8ad1e4,ecx=00000000,edx=0034ee58,esi=0034ee58,edi=e0434f4d,ebp=0034ee20,eip=7b841378,esp=0034edbc,eflags=00200212,cs=0073,ds=007b,es=007b,fs=0033,gs=003b,dr0=00000000,dr1= .. 000f: *killed* exit_code=0 --- snip --- Debuggee main thread dies. Ok. --- snip --- 000d: wait_debug_event( get_handle=1 ) 000d: wait_debug_event() = 0 { pid=000e, tid=000f, wait=(nil), event={exit_thread,code=0} } 000d: suspend_thread( handle=0xd4 ) 000d: suspend_thread() = 0 { count=0 } 000d: suspend_thread( handle=0xd8 ) 000d: suspend_thread() = 0 { count=0 } 000d: suspend_thread( handle=0xf8 ) 000d: suspend_thread() = 0 { count=0 } 000d: get_thread_context( handle=0xbc, flags=0001003f, suspend=0 ) 000d: get_thread_context() = ACCESS_DENIED { self=0, context={} } 000d: get_thread_context( handle=0xbc, flags=0001003f, suspend=0 ) 000d: get_thread_context() = ACCESS_DENIED { self=0, context={} } 000d: get_thread_context( handle=0xbc, flags=0001003f, suspend=0 ) 000d: get_thread_context() = ACCESS_DENIED { self=0, context={} } 000d: get_thread_context( handle=0xbc, flags=0001003f, suspend=0 ) 000d: get_thread_context() = ACCESS_DENIED { self=0, context={} } 000d: get_thread_context( handle=0xbc, flags=0001003f, suspend=0 ) 000d: get_thread_context() = ACCESS_DENIED { self=0, context={} } 000d: read_process_memory( handle=0xb8, addr=(nil) ) 000d: read_process_memory() = ACCESS_DENIED { data={} } .. --- snip --- Debugger wakes up, sees debuggee (main) thread termination event. Suspends remaining debuggee threads - although unnecessary due to debugging event before = already suspended. Now the problem: the debugger can't get the thread context of any debuggee threads nor process memory anymore after this point. Basically dead end here... The reason is the way server/thread.c/get_thread_context() and server/thread.c/set_thread_context() handles thread->context and thread->suspend_context data ("self" vs. "foreign" threads) child threads "self": set_thread_context() -> suspend == 1 -> thread->suspend_context filled get_thread_context(): req->suspend == 1 && thread == current && thread->suspend_context --- snip --- if (thread->context == thread->suspend_context) thread->context = NULL; set_reply_data_ptr( thread->suspend_context, sizeof(CONTEXT) ); thread->suspend_context = NULL; --- snip --- Which resets the context and suspend context data. Next time when the debugger itself tries to query the thread context of already suspended debuggee child threads it will obviously fail: "foreign" debugger thread: get_thread_context() -> suspend == 0 --- snip --- else if (thread != current && !thread->context) { /* thread is not suspended, retry (if it's still running) */ if (thread->state != RUNNING) set_error( STATUS_ACCESS_DENIED ); else set_error( STATUS_PENDING ); } --- snip --- I guess this is an oversight, a behavior not really intended? Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 5

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 July 2009