- Wine-Devel - list.winehq.org

Tools for identifying what a DLL provides?
by David D. Hagood March 1, 2005

March 1, 2005

I have a DLL from a manufacturer that I don't have the source for, nor do I have the header or the import library for. Since Wine developers frequently have to reverse engineer what a given DLL provides, does anybody have a good recommendation for a tool that can scan the DLL and report what functions it exports, and their arg types and return types?

4 4

Re: [wined3d] texture interface separation.
by Oliver Stieber March 1, 2005

March 1, 2005

2 1

Re: Wine cabinet.dll FDI Conformace Test Patch
by Daniel Kegel March 1, 2005

March 1, 2005

Andreas wrote: > It's an unspoken rule that preprocessor directives (#ifdef, ...) > always start at the very beginning of a line to make sure one recognizes > immediately which parts of the code are being processed and which ones aren't. Good point. I should have caught that style violation when I reviewed their code for them this weekend. > AFAICS you're not using wine test suite infrastructure, e.g. ok() etc. > > Using printf() directly strikes me as being quite bad, too... I think they're using the wine test infrastructure properly everywhere. The only exception is the disabled self-test in tvfs.c, but I think that's fine. It's not even built, it was just used while developing the test harness. > Apart from that it appears to be very good. Cool! - Dan

2 1

Re: winedbg questions
by Pouech Eric DMI AEI CAEN March 1, 2005

March 1, 2005

> I'm trying to use winedbg to run the direct sound regression > tests and have two questions: > > Execution stops when starting the first dsound.dll thread. Is > this normal? Is the stack trace with no symbol information > normal? no, because of this in your trace Couldn't initiate DbgHelp the only reason this fails is because dbghelp cannot get to the wine-loader in the running programm try to set the env var WINELOADER to the {pk}loader (full path) you're using and check again A+

1 0

winedbg questions
by Robert Reif March 1, 2005

March 1, 2005

I'm trying to use winedbg to run the direct sound regression tests and have two questions: Execution stops when starting the first dsound.dll thread. Is this normal? Is the stack trace with no symbol information normal? Typing c continues to the exception I am interested in but the stack trace has no symbolic information. This is with a modified dsound.dll that does zeroing of memory before freeing. An unmodified dsound.dll stops at the start but does not get the second exception. This is with a standard RH9 with up to date erratas and this mornings cvs. typescript log attached. Why is winedbg stopping at the first thread creation? Why is there no symbolic stack information? [wine(a)dell tests]$ WINEDEBUG=+wave,+dsound,+tid winedbg "dsound_test.exe.so dsound" WineDbg starting on pid 0xa Couldn't initiate DbgHelp 000b:trace:wave:OSS_WaveInit () 000b:trace:wave:OSS_WaveOutInit (0x41765960) /dev/dsp 000b:trace:wave:OSS_OpenDevice (0x41765960,1,(nil),0,-1,-1,ffffffff) ... 000b:warn:wave:OSS_RawOpenDevice Couldn't open /dev/dsp5 (No such device) 000b:trace:wave:OSS_widMessage (0, DRVM_INIT, 00000000, 00000000, 00000000); 000b:trace:wave:OSS_widMessage (0, WIDM_GETNUMDEVS, 00000000, 00000000, 00000000); 000b:trace:wave:OSS_wodMessage (0, DRVM_INIT, 00000000, 00000000, 00000000); 000b:trace:wave:OSS_wodMessage (0, WODM_GETNUMDEVS, 00000000, 00000000, 00000000); 000b:trace:dsound:DllMain (0x40870000 0x1 0x1) 000b:trace:dsound:DllMain DLL_PROCESS_ATTACH 000f:trace:dsound:DllMain (0x40870000 0x2 (nil)) 000f:trace:dsound:DllMain DLL_THREAD_ATTACH In 32 bit mode. 0x40471f77: pushl %esi Wine-dbg>bt Backtrace: =>1 0x40471f77 (0x4085fff4) 2 0x400298f5 (0x00000000) Wine-dbg>c dsound.c:167:Testing IDirectSound 000b:trace:dsound:DSOUND_DllGetClassObject ({47d4d946-62e8-11cf-93bc-444553540000},{00000001-0000-0000-c000-000000000046},0x4085fe30) 000b:trace:dsound:DSCF_AddRef (0x408a586c) ref was 1 000b:trace:dsound:DSCF_CreateInstance (0x408a586c)->((nil),{279afa83-4981-11ce-a521-0020af0be560},0x4085fe6c) 000b:trace:dsound:DSOUND_Create ((null),0x4085fe6c,(nil)) ... 000b:trace:wave:wodOpen OSS_OpenDevice returned this format: 22050x8x2 000b:trace:wave:wodOpen got 32 2048 byte fragments (46 ms/fragment) 000b:trace:wave:wodOpen fd=16 fragstotal=32 fragsize=2048 BufferSize=65536 001a:trace:wave:wodPlayer_ProcessMessages calling ExitThread() 001a:trace:dsound:DllMain (0x40870000 0x3 (nil)) 001a:trace:dsound:DllMain DLL_THREAD_DETACH First chance exception: page fault on read access to 0x00000000 in 32-bit code (0x401a0d88). In 32 bit mode. Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0033 GS:005f EIP:401a0d88 ESP:419d4528 EBP:419d4540 EFLAGS:00210293( - 00 RISA1C) EAX:00000008 EBX:401d63c4 ECX:00000001 EDX:402f0038 ESI:00000000 EDI:00010000 Stack dump: 0x419d4528: 00000000 00000000 00000000 401d63c4 0x419d4538: 402f0000 00010000 419d456c 401a1819 0x419d4548: 402f0000 00010000 419d455c 00000000 0x419d4558: 402f0000 00000000 405036c8 00010000 0x419d4568: 00000000 419d4584 40457b3a 402f0000 0x419d4578: 00000002 00010000 405036c8 419d45b0 Backtrace: =>1 0x401a0d88 (0x419d4540) 2 0x401a1819 (0x419d456c) 3 0x40457b3a (0x419d4584) 4 0x404561d7 (0x419d45b0) 5 0x404562bd (0x419d45d0) 6 0x404918f5 (0x419d45e4) 7 0x4045ace9 (0x419d45fc) 8 0x4045b07b (0x419d4608) 9 0x4043a0e8 (0x419d4638) 10 0x401a2c9a (0x419d4650) 11 0x401a3dd3 (0x419d46c0) 12 0x401a41a3 (0x419d46e8) 13 0x40486c8f (0x419d47b8) 14 0x401ba077 (0x419d4ff4) 15 0x401116c7 (0x00000000) 0x401a0d88: movl 0x0(%esi),%eax Wine-dbg>q WineDbg terminated on pid 0xa

1 0

Re: wine/dlls/comctl32 status.c
by Thomas Weidenmueller March 1, 2005

March 1, 2005

Alexandre Julliard wrote: >Log message: > Filip Navara <navaraf(a)reactos.com> > Implement SB_SETBORDERS. > > Just FYI: Win95, 98, 98SE, ME, NT4, NT5.0, NT5.1 and later do not support this message even though MS Office might try to use them. Best Regards, Thomas

1 0

Re: Patch for wsock32 conformance test
by Alexandre Julliard March 1, 2005

March 1, 2005

Thomas Kho <thomaskho(a)gmail.com> writes: > We're working on a set of tests for wsock32.dll with guidance from Dan > Kegel. So far we've > completed a test of blocking network I/O with multiple threads. > Attached is a patch from our efforts. We look forward to suggestions. This stuff should be merged with the other winsock tests in dlls/winsock/tests/sock.c (assuming it does something that the current tests don't, I haven't checked this). There is no point in having duplicate tests for wsock32 since it just forwards everything to ws2_32. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [programs/regedit] Use Favorit* instead of Favourit*
by Robert Shearman March 1, 2005

March 1, 2005

Paul Vriens wrote: >Hi, > >Our regedit displays Favourites in the menu. This patch changes that to >use Favorites. The patch also changes the variables with FAVOURITE in >the name. The reasoning is: > >a. Windows uses Favorite(s) all over the place. >b. We do too. > >That's the only reasoning and not if either one is better (UK/US etc..) > >No functional changes btw. > >Changelog > Change Favourite(s) into Favorite(s) > > Fair enough for strings in the English, US resources, as long as the strings in the English, Neutral resources are still spelt correctly. > Change variables containing FAVOURITE into FAVORITE > > Why do this? Rob

2 1

Crash in Polar Precision Performance Software
by Ron Jensen Feb. 28, 2005

Feb. 28, 2005

Hello, This trace is from Polar's Precision Performance Software http://www.codeweavers.com/site/compatibility/browse/name?app_id=681 running on CVS wine. This crash happens with CVS wine, and wine I compiled from http://ftp.codeweavers.com/pub/crossover/office/source/office-src-4.1.0.tgz It does not happen with the precompiled binaries in CXOffice's Loki installer. Can someone give me a clue as to were to start looking to fix this? Thanks. /*******/ wineuser$wine 'C:\Program Files\Polar\Polar 32.exe' fixme:gdi:Escape16 unknown/unsupported 16-bit escape c03 (56,0x403815de,0x40381626 fixme:gdi:Escape16 unknown/unsupported 16-bit escape c03 (56,0x403815de,0x40381626 wine: Unhandled exception (thread 0009), starting debugger... WineDbg starting on pid 0x8 Unhandled exception: page fault on read access to 0xa84c73e0 in 32-bit code (0x00415809). In 32 bit mode. Register dump: CS:0073 SS:007b DS:007b ES:007b FS:003b GS:0033 EIP:00415809 ESP:4069e63c EBP:4069e6c4 EFLAGS:00010282( - 00 - RIS1) EAX:00000000 EBX:4082f8d4 ECX:a84c73e0 EDX:000004e7 ESI:4069f3f0 EDI:00020040 Stack dump: 0x4069e63c: 00414e23 4069f3f0 000004e7 00020040 0x4069e64c: 4069f3f0 4069e6c4 4082f8d4 004144c9 0x4069e65c: 00020040 4069f3f0 000004e7 0052c3ec 0x4069e66c: 00020040 00000638 00020040 000000a0 0x4069e67c: 00020040 408517a8 4069e6c4 4082f8d4 0x4069e68c: 403d6a28 403d6980 00000000 4007aa04 Backtrace: =>1 0x00415809 in polar 32 (+0x15809) (0x4069e6c4) 2 0x407ae6c0 WINPROC_CallWndProc+0x70(msg=0x4e, wParam=0x0, lParam=0x4069edf0) [/home/wineuser/src/wine/dlls/user/../../windows/winproc.c:419] in user32 (0x4069e700) 3 0x407b393e CallWindowProcA+0xfe(func=0x408517a8, hwnd=0x20040, msg=0x4e, wParam=0x0, lParam=0x4069edf0) [/home/wineuser/src/wine/dlls/user/../../windows/winproc.c:2940] in user32 (0x4069e72c) 4 0x4078ff36 DefDlgProcA(hwnd=0x20040, msg=0x4e, wParam=0x0, lParam=0x4069edf0) [/home/wineuser/src/wine/dlls/user/../../windows/defdlg.c:453] in user32 (0x4069e75c) 5 0x407ae277 WINPROC_wrapper+0x17 in user32 (0x4069e780) 6 0x407ae6c0 WINPROC_CallWndProc+0x70(msg=0x4e, wParam=0x0, lParam=0x4069edf0) [/home/wineuser/src/wine/dlls/user/../../windows/winproc.c:419] in user32 (0x4069e7bc) 7 0x407b3be4 CallWindowProcW+0x184(func=0x4085145a, hwnd=0x20040, msg=0x4e, wParam=0x0, lParam=0x4069edf0) [/home/wineuser/src/wine/dlls/user/../../windows/winproc.c:3053] in user32 (0x4069eca0) 8 0x407e1d13 call_window_proc+0xc3(wparam=0x0, lparam=0x4069edf0, unicode=0x1, same_thread=0x1) [/home/wineuser/src/wine/dlls/user/message.c:1475] in user32 (0x4069ed00) 9 0x407e1eef SendMessageTimeoutW+0x14f(hwnd=0x20040, msg=0x4e, wparam=0x0, lparam=0x4069edf0, flags=0x0, timeout=0xffffffff, res_ptr=0x4069ed80) [/home/wineuser/src/wine/dlls/user/message.c:1989] in user32 (0x4069ed5c) 10 0x407e1f35 SendMessageW(hwnd=0x20040, msg=0x4e, wparam=0x0, lparam=0x4069edf0) [/home/wineuser/src/wine/dlls/user/message.c:2070] in user32 (0x4069ed88) 11 0x406eee3b PROPSHEET_SetCurSel(skipdir=0x1, hpage=0x403e2cd0) [/home/wineuser/src/wine/dlls/comctl32/propsheet.c:2102] in comctl32 (0x4069ee0c) 12 0x406f26c4 PROPSHEET_DialogProc(hwnd=0x4002e, uMsg=0x110, wParam=0x0, lParam=0x403e2328) [/home/wineuser/src/wine/dlls/comctl32/propsheet.c:3379] in comctl32 (0x4069f3f0) 13 0x407ae277 WINPROC_wrapper in user32 (0x4069f414) 14 0x407ae6c0 WINPROC_CallWndProc(msg=0x110, wParam=0x0, lParam=0x403e2328) [/home/wineuser/src/wine/dlls/user/../../windows/winproc.c:419] in user32 (0x4069f450) 15 0x407b393e CallWindowProcA+0xfe(func=0x40851794, hwnd=0x4002e, msg=0x110, wParam=0x0, lParam=0x403e2328) [/home/wineuser/src/wine/dlls/user/../../windows/winproc.c:2940] in user32 (0x4069f47c) 16 0x4078ff36 DefDlgProcA(hwnd=0x4002e, msg=0x110, wParam=0x0, lParam=0x403e2328) [/home/wineuser/src/wine/dlls/user/../../windows/defdlg.c:453] in user32 (0x4069f4ac) 17 0x407ae277 WINPROC_wrapper+0x17 in user32 (0x4069f4d0) 18 0x407ae6c0 WINPROC_CallWndProc+0x70(msg=0x110, wParam=0x0, lParam=0x403e2328) [/home/wineuser/src/wine/dlls/user/../../windows/winproc.c:419] in user32 (0x4069f50c) 19 0x407b3be4 CallWindowProcW+0x184(func=0x4085145a, hwnd=0x4002e, msg=0x110, wParam=0x0, lParam=0x403e2328) [/home/wineuser/src/wine/dlls/user/../../windows/winproc.c:3053] in user32 (0x4069f9f0) 20 0x407e1d13 call_window_proc+0xc3(wparam=0x0, lparam=0x403e2328, unicode=0x1, same_thread=0x1) [/home/wineuser/src/wine/dlls/user/message.c:1475] in user32 (0x4069fa50) 21 0x407e1eef SendMessageTimeoutW+0x14f(hwnd=0x4002e, msg=0x110, wparam=0x0, lparam=0x403e2328, flags=0x0, timeout=0xffffffff, res_ptr=0x4069fad0) [/home/wineuser/src/wine/dlls/user/message.c:1989] in user32 (0x4069faac) 22 0x407e1f35 SendMessageW(hwnd=0x4002e, msg=0x110, wparam=0x0, lparam=0x403e2328) [/home/wineuser/src/wine/dlls/user/message.c:2070] in user32 (0x4069fad8) 23 0x4079427e DIALOG_CreateIndirect(owner=0x1004e, dlgProc=0x406f1780, param=0x403e2328, unicode=0x0, modal=0x1) [/home/wineuser/src/wine/dlls/user/../../windows/dialog.c:667] in user32 (0x4069fbe4) 24 0x407946d9 DialogBoxIndirectParamAorW+0x39(hInstance=0x400000, template=0x403e17a8, owner=0x1004e, dlgProc=0x406f1780, param=0x403e2328, flags=0x2) [/home/wineuser/src/wine/dlls/user/../../windows/dialog.c:841] in user32 (0x4069fc08) 25 0x4079476b DialogBoxIndirectParamA(hInstance=0x400000, template=0x403e17a8, owner=0x1004e, dlgProc=0x406f1780, param=0x403e2328) [/home/wineuser/src/wine/dlls/user/../../windows/dialog.c:852] in user32 (0x4069fc2c) 26 0x406edb53 PROPSHEET_CreateDialog [/home/wineuser/src/wine/dlls/comctl32/propsheet.c:729] in comctl32 (0x4069fc5c) 27 0x406f0961 PropertySheetA+0x2d1(lppsh=0x4069fca4) [/home/wineuser/src/wine/dlls/comctl32/propsheet.c:2794] in comctl32 (0x4069fc80) 28 0x00414354 in polar 32 (+0x14354) (0x00000111) 29 0x00000000 (0x00000000) 0x00415809: cmpl %edx,0x0(%ecx) Wine-dbg>quit WineDbg terminated on pid 0x8

2 2

Help with winebuild/winegcc
by Ivan Leo Puoti Feb. 28, 2005

Feb. 28, 2005

Hello, I'm trying to get a program in the programs/ directory to export symbols, I've added -shared path/to/spec/spec.c to the linker command, but I now get a segmentation fault at startup. Can someone knowledgeable about winegcc/winebuild give me a suggestion/solution? I'm really stuck because of this and can't get on with safedisc support. Ivan.

1 0