November 2003 - Wine-Devel - list.winehq.org

Map and Guide & ADO
by Olaf Leidinger Nov. 18, 2003

Nov. 18, 2003

Hello! I'm trying to run MAP and Guide 9.0, but it needs ADO V.2.5 So I tried to install mdac from Microsoft, but both version 2.5 and 2.6 crash before installing anything. I've extracted the cabs and installed everything, but it would be cool to have the registry entries added by the installer, so that M&G knows, that ADO is there. Does anybody have an idea of what to do? Ciao, Olaf Information follows: fake_windows with working IE 5.5 wine 20031016. mdac_type v. 2.5 trace:loaddll:load_dll Loaded module L"ADVAPI32.dll" : builtin trace:loaddll:load_dll Loaded module L"GDI32.dll" : builtin trace:loaddll:load_dll Loaded module L"USER32.dll" : builtin trace:loaddll:load_dll Loaded module L"C:\\WINDOWS\\SYSTEM\\COMCTL32.dll" : builtin trace:loaddll:load_dll Loaded module L"x11drv.dll" : builtin trace:loaddll:load_dll Loaded module L"C:\\Program Files\\mg9\\prog\\IXP026.TMP\\dasetupr.dll" : native trace:loaddll:load_dll Loaded module L"C:\\WINDOWS\\SYSTEM\\ole32.dll" : native trace:loaddll:load_dll Loaded module L"lz32.dll" : builtin trace:loaddll:load_dll Loaded module L"VERSION.dll" : builtin trace:loaddll:load_dll Loaded module L"C:\\Program Files\\mg9\\prog\\IXP026.TMP\\advpack.dll" : native trace:loaddll:load_dll Loaded module L"C:\\Program Files\\mg9\\prog\\IXP026.TMP\\CABINET.DLL" : native trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\Program Files\\mg9\\prog\\IXP026.TMP\\CABINET.DLL" : native trace:loaddll:load_dll Loaded module L"C:\\WINDOWS\\SYSTEM\\shlwapi.dll" : builtin trace:loaddll:load_dll Loaded module L"C:\\WINDOWS\\SYSTEM\\SHELL32.dll" : builtin trace:loaddll:load_dll Loaded module L"C:\\WINDOWS\\SYSTEM\\winspool.drv" : builtin trace:loaddll:load_dll Loaded module L"C:\\WINDOWS\\SYSTEM\\comdlg32.dll" : builtin trace:loaddll:load_dll Loaded module L"C:\\Program Files\\mg9\\prog\\IXP026.TMP\\CFGMGR32.dll" : native trace:loaddll:load_dll Loaded module L"MPR.dll" : builtin trace:loaddll:load_dll Loaded module L"C:\\WINDOWS\\SYSTEM\\RPCRT4.dll" : nativetrace:loaddll:load_dll Loaded module L"C:\\Program Files\\mg9\\prog\\IXP026.TMP\\SETUPAPI.DLL" : native trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\Program Files\\mg9\\prog\\IXP026.TMP\\SETUPAPI.DLL" : native trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\WINDOWS\\SYSTEM\\RPCRT4.dll" : native trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\WINDOWS\\SYSTEM\\mpr.dll" : builtin trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\Program Files\\mg9\\prog\\IXP026.TMP\\CFGMGR32.dll" : native trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\WINDOWS\\SYSTEM\\comdlg32.dll" : builtin trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\WINDOWS\\SYSTEM\\winspool.drv" : builtin trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\WINDOWS\\SYSTEM\\shell32.dll" : builtin trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\WINDOWS\\SYSTEM\\shlwapi.dll" : builtin trace:loaddll:load_dll Loaded module L"C:\\Program Files\\mg9\\prog\\IXP026.TMP\\CABINET.DLL" : native trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\Program Files\\mg9\\prog\\IXP026.TMP\\CABINET.DLL" : native wine: Unhandled exception (thread 000b), starting debugger... trace:loaddll:load_dll Loaded module L"advapi32.dll" : builtin WineDbg starting on pid a No debug information in ELF 'wine' ((nil)) Breakpoint 1 at 0x492591a0 No debug information in ELF '/usr/lib/wine/lib/libwine.so.1' (0x40001000) Loaded debug information from ELF '/usr/lib/wine/lib/wine/ntdll.dll.so' (0x40019000) No debug information in ELF '/usr/lib/wine/lib/libwine_unicode.so.1' (0x40083000) No debug information in ELF '/lib/libnss_compat.so.2' (0x40191000) Loaded debug information from ELF '/usr/lib/wine/lib/wine/kernel32.dll.so' (0x402b0000) Loaded debug information from ELF '/usr/lib/wine/lib/wine/advapi32.dll.so' (0x40813000) Loaded debug information from ELF '/usr/lib/wine/lib/wine/gdi32.dll.so' (0x40842000) Loaded debug information from ELF '/usr/lib/wine/lib/wine/user32.dll.so' (0x408be000) Loaded debug information from ELF '/usr/lib/wine/lib/wine/comctl32.dll.so' (0x409fb000) Loaded debug information from ELF '/usr/lib/wine/lib/wine/x11drv.dll.so' (0x40aa2000) No debug information in ELF '/usr/lib/libGL.so.1' (0x40b1f000) No debug information in ELF '/usr/lib/libGLcore.so.1' (0x40b88000) *** Invalid address 0xf6cc6000 (_end+0xb61c05d0) No debug information in ELF '/usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2' (0x4018b000) No debug information in ELF '/usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2' (0x410fd000) No debug information in ELF '/usr/lib/gconv/ISO8859-15.so' (0x4018e000) Loaded debug information from ELF '/usr/lib/wine/lib/wine/version.dll.so' (0x41790000) Loaded debug information from ELF '/usr/lib/wine/lib/wine/lz32.dll.so' (0x40b06000) Loaded debug information from ELF '/usr/lib/wine/lib/wine/setupx.dll.so' (0x41c3a000) No debug information in ELF '/lib/libnss_files.so.2' (0x41e1c000) No debug information in 32bit DLL 'C:\Program Files\mg9\prog\IXP026.TMP\dasetup.exe' (0x1000000) No debug information in 32bit DLL 'NTDLL.DLL' (0x40030000) No debug information in 32bit DLL 'KERNEL32.DLL' (0x402e0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' (0x40820000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' (0x40860000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x408e0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' (0x40a10000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40ab0000) No debug information in 32bit DLL 'C:\PROGRAM FILES\MG9\PROG\IXP026.TMP\DASETUPR.DLL' (0x400000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x65f00000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\LZ32.DLL' (0x40b10000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\VERSION.DLL' (0x417a0000) No debug information in 32bit DLL 'C:\PROGRAM FILES\MG9\PROG\IXP026.TMP\ADVPACK.DLL' (0x70e90000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SETUPAPI.DLL' (0x41c50000) Unhandled exception: privileged instruction in 32-bit code (0x493458ed). In 32-bit mode. 0x493458ed (NTDLL.DLL.memcpy+0x67d8d): movl %gs:0x418,%eax First chance exception: privileged instruction in 32-bit code (0x493458ed). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:008f GS:14d7 EIP:493458ed ESP:40804de8 EBP:40804dec EFLAGS:00210302( R- 00 IT - - 1 ) EAX:00000001 EBX:49389de0 ECX:49494854 EDX:00002014 ESI:00002014 EDI:00000000 Stack dump: 0x40804de8 (_end+0x44a1dc): 49389de0 4080543c 492aca1c 00002014 0x40804df8 (_end+0x44a1ec): 49494851 00000000 00000000 00000000 0x40804e08 (_end+0x44a1fc): 00000000 00000000 00000000 00000000 0x40804e18 (_end+0x44a20c): 00000000 00000000 00000000 00000000 0x40804e28 (_end+0x44a21c): 00000000 49494852 40804fdc 00000000 0x40804e38 (_end+0x44a22c): 492af4e5 4080541c 00000000 00000000 0x40804e48 (_end+0x44a23c): 0011: sel=008f base=400812e0 limit=00000fff 32-bit rw- Backtrace: =>0 0x493458ed (NTDLL.DLL.memcpy+0x67d8d) (ebp=40804dec) 1 0x492aca1c (NTDLL.DLL.strtoul+0x1b17c) (ebp=4080543c) 2 0x492c823c (NTDLL.DLL.vsprintf+0x8c) (ebp=4080551c) 3 0x492b588d (NTDLL.DLL.sprintf+0x2d) (ebp=4080553c) 4 0x49437e36 (NTDLL.DLL.sqrt+0x9f5f6) (ebp=408095ac) 5 0x49437b7d (NTDLL.DLL.sqrt+0x9f33d) (ebp=40809dfc) 6 0x49407709 (NTDLL.DLL.sqrt+0x6eec9) (ebp=40809f3c) 7 0x494078d3 (NTDLL.DLL.sqrt+0x6f093) (ebp=40809f5c) 8 0x49407a49 (NTDLL.DLL.sqrt+0x6f209) (ebp=40809f8c) 9 0x40aebe75 (X11DRV_SetWindowText+0x245(hwnd=0x10034, text=0x402033a8) [window.c:841] in x11drv.dll.so) (ebp=40809fe4) 10 0x4092e4f6 (DEFWND_SetTextA+0x176(hwnd=0x10034, text=0x4080c32c) [defwnd.c:108] in user32.dll.so) (ebp=4080a08c) 11 0x4092ff27 (DefWindowProcA+0x187(hwnd=0x10034, msg=0xc, wParam=0x0, lParam=0x4080c32c) [defwnd.c:817] in user32.dll.so) (ebp=4080a0d8) 12 0x409207e9 (.L67+0x6d [static.c] in user32.dll.so) (ebp=4080a148) 13 0x40920cf5 (StaticWndProcA+0x65(hWnd=0x10034, uMsg=0xc, wParam=0x0, lParam=0x4080c32c) [static.c:411] in user32.dll.so) (ebp=4080a16c) 14 0x40959d6f (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=4080a190) 15 0x40959de7 (WINPROC_CallWndProc+0x67(proc=0x40920c90, hwnd=0x10034, msg=0xc, wParam=0x0, lParam=0x4080c32c) [winproc.c:229] in user32.dll.so) (ebp=4080a1c4) 16 0x409600fb (CallWindowProcA+0xeb(func=0x40920c90, hwnd=0x10034, msg=0xc, wParam=0x0, lParam=0x4080c32c) [winproc.c:2898] in user32.dll.so) (ebp=4080a1f4) 17 0x40972fd0 (call_window_proc+0x170(hwnd=0x10034, msg=0xc, wparam=0x0, lparam=0x4080c32c, unicode=0x0, same_thread=0x1) [message.c:1453] in user32.dll.so) (ebp=4080a250) 18 0x40974020 (SendMessageTimeoutA+0x240(hwnd=0x10034, msg=0xc, wparam=0x0, lparam=0x4080c32c, flags=0x0, timeout=0xffffffff, res_ptr=0x4080a2e0) [message.c:1959] in user32.dll.so) (ebp=4080a2bc) 19 0x40974102 (SendMessageA+0x52(hwnd=0x10034, msg=0xc, wparam=0x0, lparam=0x4080c32c) [message.c:2004] in user32.dll.so) (ebp=4080a2e8) 20 0x4093273c (SendDlgItemMessageA+0x4c(hwnd=0x10032, id=0x3ee, msg=0xc, wParam=0x0, lParam=0x4080c32c) [dialog.c:1139] in user32.dll.so) (ebp=4080a304) 21 0x01005e66 (dasetup.exe..text+0x4e66 in dasetup.exe) (ebp=4080e330) 22 0x010091bb (dasetup.exe..text+0x81bb in dasetup.exe) (ebp=4080e350) 23 0x40959d6f (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=4080e374) 24 0x40959de7 (WINPROC_CallWndProc+0x67(proc=0x100916f, hwnd=0x10032, msg=0x4fb, wParam=0x0, lParam=0x41298e88) [winproc.c:229] in user32.dll.so) (ebp=4080e3a8) 25 0x409600fb (CallWindowProcA+0xeb(func=0x409ea930, hwnd=0x10032, msg=0x4fb, wParam=0x0, lParam=0x41298e88) [winproc.c:2898] in user32.dll.so) (ebp=4080e3d8) 26 0x4092dec8 (DefDlgProcA+0x68(hwnd=0x10032, msg=0x4fb, wParam=0x0, lParam=0x41298e88) [defdlg.c:354] in user32.dll.so) (ebp=4080e404) 27 0x40959d6f (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=4080e428) 28 0x40959de7 (WINPROC_CallWndProc+0x67(proc=0x4092de60, hwnd=0x10032, msg=0x4fb, wParam=0x0, lParam=0x41298e88) [winproc.c:229] in user32.dll.so) (ebp=4080e45c) 29 0x4095fb68 (WINPROC_CallProc32WTo32A+0x68(func=0x4092de60, hwnd=0x10032, msg=0x4fb, wParam=0x0, lParam=0x41298e88) [winproc.c:2718] in user32.dll.so) (ebp=4080e48c) 30 0x4096020b (CallWindowProcW+0xeb(func=0x409ea4f8, hwnd=0x10032, msg=0x4fb, wParam=0x0, lParam=0x41298e88) [winproc.c:2937] in user32.dll.so) (ebp=4080e4bc) 31 0x4093dd8b (DispatchMessageW+0xbb(msg=0x4080e524) [message.c:888] in user32.dll.so) (ebp=4080e4f0) 32 0x40932411 (.L313+0x19 [dialog.c] in user32.dll.so) (ebp=4080e514) 33 0x40974e34 (IsDialogMessageA+0x64(hwndDlg=0x10021, pmsg=0x40812da0) [message.c:2395] in user32.dll.so) (ebp=4080e54c) 34 0x40a53ce1 (PROPSHEET_IsDialogMessage+0x91(hwnd=0x10021, lpMsg=0x40812da0) [propsheet.c:2709] in comctl32.dll.so) (ebp=4080e574) 35 0x40a54799 (PROPSHEET_DialogProc+0x7e9(hwnd=0x10021, uMsg=0x475, wParam=0x0, lParam=0x40812da0) [propsheet.c:3051] in comctl32.dll.so) (ebp=4080e7ac) 36 0x40959d6f (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=4080e7d0) 37 0x40959de7 (WINPROC_CallWndProc+0x67(proc=0x40a53fb0, hwnd=0x10021, msg=0x475, wParam=0x0, lParam=0x40812da0) [winproc.c:229] in user32.dll.so) (ebp=4080e804) 38 0x409600fb (CallWindowProcA+0xeb(func=0x409ea8c4, hwnd=0x10021, msg=0x475, wParam=0x0, lParam=0x40812da0) [winproc.c:2898] in user32.dll.so) (ebp=4080e834) 39 0x4092dec8 (DefDlgProcA+0x68(hwnd=0x10021, msg=0x475, wParam=0x0, lParam=0x40812da0) [defdlg.c:354] in user32.dll.so) (ebp=4080e860) 40 0x40959d6f (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=4080e884) 41 0x40959de7 (WINPROC_CallWndProc+0x67(proc=0x4092de60, hwnd=0x10021, msg=0x475, wParam=0x0, lParam=0x40812da0) [winproc.c:229] in user32.dll.so) (ebp=4080e8b8) 42 0x409600fb (CallWindowProcA+0xeb(func=0x4092de60, hwnd=0x10021, msg=0x475, wParam=0x0, lParam=0x40812da0) [winproc.c:2898] in user32.dll.so) (ebp=4080e8e8) 43 0x40972fd0 (call_window_proc+0x170(hwnd=0x10021, msg=0x475, wparam=0x0, lparam=0x40812da0, unicode=0x0, same_thread=0x1) [message.c:1453] in user32.dll.so) (ebp=4080e944) 44 0x40974020 (SendMessageTimeoutA+0x240(hwnd=0x10021, msg=0x475, wparam=0x0, lparam=0x40812da0, flags=0x0, timeout=0xffffffff, res_ptr=0x4080e9d4) [message.c:1959] in user32.dll.so) (ebp=4080e9b0) 45 0x40974102 (SendMessageA+0x52(hwnd=0x10021, msg=0x475, wparam=0x0, lparam=0x40812da0) [message.c:2004] in user32.dll.so) (ebp=4080e9dc) 46 0x01005611 (dasetup.exe..text+0x4611 in dasetup.exe) (ebp=40812de0) 47 0x01009612 (dasetup.exe.EntryPoint+0x152 in dasetup.exe) (ebp=40812e6c) 48 0x400537a5 (LdrInitializeThunk+0x2b5(main_file=0x4, CreateFileW_ptr=0x402f90d0, unknown3=0x0, unknown4=0x0) [loader.c:1845] in ntdll.dll.so) (ebp=40812f20) 49 0x40332613 (start_process+0xb3(arg=0x0) [process.c:171] in kernel32.dll.so) (ebp=40812ff4) 50 0x40005101 (dasetup.exe..rsrc+0x3efd8101 in libwine.so.1) (ebp=00000000) 0x493458ed (NTDLL.DLL.memcpy+0x67d8d): movl %gs:0x418,%eax

1 0

Delay setting breakpoints
by Shachar Shemesh Nov. 18, 2003

Nov. 18, 2003

Hi list, Does anyone remeber how to delay setting a breakpoint in GDB? Due to human-machine incompatibilities, I am using GDB rather than winedbg, and setting breakpoints inside the actual program would be greatly simplified if I could ask for the breakpoint before starting Wine. Can anyone point me again to the doc describing running winedbg as a gdb backend? Shachar -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

3 2

Mac OS X Compilation broken
by Pierre d'Herbemont Nov. 18, 2003

Nov. 18, 2003

Hi! I am getting trouble on Mac OS X with a modification to WineBuild. Here is the patch I am refering to: http://cvs.winehq.com/patch.py?id=9949 I'd like to know to what symbol "_end" should refer to? "_end" is flagged as an external symbol in the spec.c file, but I don't see any definition of it. I am getting the following error when launching wine: iMac:~ steg$ wine wine: failed to initialize: dlcompat: dyld: wine Undefined symbols: __end In fact the error appears when loading ntdll. Any idea? Thanks, Pierre

2 1

Re: Reject wildcards in directory names
by Paul Millar Nov. 18, 2003

Nov. 18, 2003

Hi Hans, Which conformance tests fail currently? I don't see any problems with the kernel DLL tests right at the moment, which is somewhat disconcerting. I do see a problem with the listbox tests (in the user dll tests). There's also various bugs in pipe tests (under kernel) that mysteriously vanished after closing my eyes and counting to ten: http://www.astro.gla.ac.uk/users/paulm/WRT/wrt.php Anyone have any idea what might have happened? Cheers, Paul. On Mon, 17 Nov 2003, Hans Leidekker wrote: > This makes Wine pass the kernel directory conformance test without failures. ---- Paul Millar

3 5

Where has Freetype config gone?
by Shachar Shemesh Nov. 18, 2003

Nov. 18, 2003

When trying to compile CVS Wine, I don't have freetype support. The configure script claims that I don't have freetype-dev installed (I do). configure.log shows the message: In file included from conftest.c:95: /usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' hasn't been included yet!" /usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always use macros to include FreeType header files." /usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:" /usr/include/freetype2/freetype/freetype.h:23:2: #error " #include <ft2build.h>" /usr/include/freetype2/freetype/freetype.h:24:2: #error " #include FT_FREETYPE_H" This message repeats several times (for several tests). My system is a Debian Sid, and I have freetype2-dev installed properly. -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

2 2

Re: Small winedefault.reg changes
by Alexandre Julliard Nov. 18, 2003

Nov. 18, 2003

Francois Gouget <fgouget(a)codeweavers.com> writes: > [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug] > # command line to start a debugger when an exception occurs > -"Debugger"="winedbg --debugmsg -all %ld %ld" > +"Debugger"="winedbg.exe --debugmsg -all %ld %ld" This shouldn't make any difference; if it does it's a bug. > [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0002E005-0000-0000-C000-000000000046}\InProcServer32] > -@="comcat.dll" > +@="C:\\Windows\\System\\comcat.dll" This is wrong, the system directory is not necessarily c:\windows\system. -- Alexandre Julliard julliard(a)winehq.com

1 0

re: Potential forum at linuxquestions.org
by Dan Kegel Nov. 18, 2003

Nov. 18, 2003

Mike Hearn wrote: > > It's not meant to replace wine-users, and especially not wine-devel of > course. > > Why a forum rather than a mailing list? That question, plus all the 'advantages' you list, indicate that you do indeed intend it to replace wine-users, at least for some users. A web interface that let you post to the mailing list would be fine. A web forum would not. It would mean that, if I wanted to answer user questions, I'd have to get used to another strange interface that probably has crappy indexing and is full of fruity HTML that gets in the way. I have read linuxquestions.org a bit, and don't like it much; I dislike the idea of encouraging people to use closed discussion forums like that, which don't support any sort of external archiving. Now, if you want to make things easier for users, there's room for improvement on the winehq forums page. For starters, the Forums link on the main page is buried a bit; it ought to be higher up (say, right after FAQ; the HowTo link should be part of Documentation). On the Forums page, the wine-users(a)winehq.com list should probably be the first thing on the page. The newsgroup link is currently wrong(!); it's currently news://comp.emulators.ms-windows.wine/ but should be news:comp.emulators.ms-windows.wine And we should probably link to the newsgroups at gmane.org, too. Shall I prepare patches for the website to implement these changes so people can see what I'm suggesting? - Dan

5 7

Re: dutch keyboard support
by Dmitry Timoshkov Nov. 18, 2003

Nov. 18, 2003

"grant williamson" <traxtopel(a)fastmail.fm> wrote: > This patch offers better wine support for Dutch Keyboards. > Most IBM computers sold in the Netherlands have Dutch keyboards. Well, then it would be nice to see the patch generated against current CVS, since the code has changed a bit. > Can this be included please. Also, provide a reference to an actual X keyboard layout (setxkbmap xxx) and avoid phrasing like "contributed by xxx". Please. -- Dmitry.

2 2

Netmeeting under wine
by David Martinez Prado Nov. 18, 2003

Nov. 18, 2003

Hi all! i am, trying to run netmeeting under Wine. i installed wine with the default windows partition. Then, i execute netmeeting installer and crashed. i am working on RH7.2. Can anyone help me? thank you very much. _________________________________________________________________ Descárgate en tu teléfono los tonos y logos de las canciones y artistas de más éxito en MSN Móviles. http://www.msn.es/MSNMovil/

6 9

listview advice needed.
by Rein Klazes Nov. 18, 2003

Nov. 18, 2003

Hi, Agent 2.0 beta crashes on listview related code, and requires native comctl32 to run. Here is a cut from a +relay,+message,+listview trace: | trace:message:SPY_ExitMessage (0x1004b) L"{SysListView32}" message [1004] LVM_GETITEMCOUNT returned 00000000 | 0009:Ret user32.SendMessageA() retval=00000000 ret=005cad80 At this point the listview is newly created, headers column inserted etc. No items yet. | 0009:Call user32.SendMessageA(0001004b,00001007,00000000,406cf6f8) ret=005cc1b4 | trace:message:SPY_EnterMessage (0x1004b) L"{SysListView32}" message [1007] LVM_INSERTITEMA sent from self wp=00000000 lp=406cf6f8 | trace:message:SPY_DumpMem LVITEM [0000] 00000003 00000000 00000000 00000000 | trace:message:SPY_DumpMem LVITEM [0010] 00000000 42103914 00000018 ffffffff | trace:message:SPY_DumpMem LVITEM [0020] 61737365 005cc11f 406cf770 006b30b6 | trace:message:SPY_DumpMem LVITEM [0030] ffffffff The program inserts the first item. Valid fields are Text and Image. | trace:listview:LISTVIEW_WindowProc (uMsg=1007 wParam=0 lParam=406cf6f8) | trace:listview:LISTVIEW_InsertItemT (lpLVItem={iItem=0, iSubItem=0, pszText="application/octet-stream", cchTextMax=24, iImage=-1}, isW=0) | trace:listview:LISTVIEW_InsertItemT inserting at 0, sorted=1, count=0, iItem=0 | trace:listview:LISTVIEW_ShiftIndices Shifting 0u, 1 steps | trace:listview:set_main_item () | trace:listview:set_main_item oldState=0, newState=0 | trace:listview:set_main_item uChanged=0x3 | trace:listview:notify_listview (code=-102, plvnm=iItem=0, iSubItem=0, uNewState=0x0, uOldState=0x0, uChanged=0x0, ptAction=(0, 0), lParam=0 ) | trace:listview:notify_hdr (code=-102) | trace:message:SPY_EnterMessage (0x10049) L"{wxWindowClass}" message [004e] WM_NOTIFY sent from self wp=00001e68 lp=406cf148 | trace:message:SPY_DumpStructure NMHDR hwndFrom=0x1004b idFrom=0x00001e68 code=LVN_INSERTITEM<0xffffff9a>, extra=0x20 | trace:message:SPY_DumpMem NM extra [0000] 00000000 00000000 00000000 00000000 | trace:message:SPY_DumpMem NM extra [0010] 00000000 00000000 00000000 00000000 Still inside the LVM_ISERTITEMA message a WM_NOTIFY is sent. The programs message handler queries number of items: | 0009:Call user32.SendMessageA(0001004b,00001004,00000000,00000000) ret=005cad80 | trace:message:SPY_EnterMessage (0x1004b) L"{SysListView32}" message [1004] LVM_GETITEMCOUNT sent from self wp=00000000 lp=00000000 | trace:listview:LISTVIEW_WindowProc (uMsg=1004 wParam=0 lParam=0) | trace:message:SPY_ExitMessage (0x1004b) L"{SysListView32}" message [1004] LVM_GETITEMCOUNT returned 00000001 | 0009:Ret user32.SendMessageA() retval=00000001 ret=005cad80 there is one item. | 0009:Call user32.SendMessageA(0001004b,00001005,00000000,406cebe0) ret=005ca4cb | trace:message:SPY_EnterMessage (0x1004b) L"{SysListView32}" message [1005] LVM_GETITEMA sent from self wp=00000000 lp=406cebe0 | trace:message:SPY_DumpMem LVITEM [0000] 00000004 00000000 42100a50 406cf148 | trace:message:SPY_DumpMem LVITEM [0010] 406cf154 406ced10 407c1c09 005cad80 | trace:message:SPY_DumpMem LVITEM [0020] 0001004b 00001004 406ced10 005ccb9a | trace:message:SPY_DumpMem LVITEM [0030] 0001004b and request that lParam of that item. Note that iItem is zero but iSubItem is 0x42100a50, like all other fields it is filled with rubbish. (confirmed with dissassembly that only the mask and iItem fields are filled in) | trace:listview:LISTVIEW_WindowProc (uMsg=1005 wParam=0 lParam=406cebe0) | trace:listview:LISTVIEW_GetItemT (lpLVItem={iItem=0, iSubItem=1108347472, lParam=1004b}, isW=0) | trace:message:SPY_ExitMessage (0x1004b) L"{SysListView32}" message [1005] LVM_GETITEMA returned 00000001 | trace:message:SPY_DumpMem LVITEM [0000] 00000004 00000000 42100a50 406cf148 | trace:message:SPY_DumpMem LVITEM [0010] 406cf154 406ced10 407c1c09 005cad80 | trace:message:SPY_DumpMem LVITEM [0020] 0001004b 00001004 406ced10 005ccb9a | trace:message:SPY_DumpMem LVITEM [0030] 0001004b At return, the requested value of lParam is still rubbish, which is causing a crash somewhat later. | trace:message:SPY_ExitMessage (0x10049) L"{wxWindowClass}" message [004e] WM_NOTIFY returned 00000000 | trace:message:SPY_DumpStructure NMHDR hwndFrom=0x1004b idFrom=0x00001e68 code=LVN_INSERTITEM<0xffffff9a>, extra=0x20 | trace:message:SPY_DumpMem NM extra [0000] 00000000 00000000 00000000 00000000 | trace:message:SPY_DumpMem NM extra [0010] 00000000 00000000 00000000 00000000 | 0009:Ret user32.SendMessageW() retval=00000000 ret=40b49738 If I hack LISTVIEW_GetItemT() with a hack like: | | if (lpSubItem) | { | SUBITEM_INFO *lpSubItem = LISTVIEW_GetSubItemPtr(hdpaSubItems, lpLVItem->iSubItem); | pItemHdr = lpSubItem ? &lpSubItem->hdr : &callbackHdr; |+ if(!lpSubItem) lpLVItem->iSubItem = 0; | } the program proceeds (crashes much much later) . But this is probably not the correct way to check that an invalid subitem has been passed (for instance I don't understand the callbackHdr stuff above). Any suggestion what is the correct fix? Full log at www.xs4all.nl/~rklazes/temp/agent.log.bz2 Rein. -- Rein Klazes rklazes(a)xs4all.nl

2 5