[Bug 2737] Poser 4 does not show the labels for controls = font problem?

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=2737





------- Additional Comments From marcus at jet.franken.de  2005-08-10 02:25 -------
From: Cliff Coles <bzylywq02 at sneakemail.com>                                                                                                
To: wine-bugs at winehq.org                                                                                                                    
Subject: Re: [Bug 2737] Poser 4 does not show the labels for controls = font                                                                
 problem?                                                                                                                                   
Reply-To: wine-devel at winehq.org                                                                                                             
 
(Background: Poser 4 installed with wine 2005-02-11. It works, with 
exception of font bugs as described.) 
 
I've just tried wine 20050930. When run without modification ['cd 
$POSER_DIR; wine Poser.exe'], the program no longer works. I see the 
splash screen, and the typical initialization reports, but shortly 
after, the window disappears. This is what's left on the command line: 
 
err:module:import_dll Library MSVCIRT.dll (which is needed by 
L"C:\\Program Files\\MetaCreations\\Poser 
4\\Runtime\\Plugins\\FFMS.arp") not found 
err:seh:EXC_DefaultHandling Exception frame is not in stack limits => 
unable to dispatch exception. 
 
If I copy the MSVCIRT.dll from my Win2k system32 directory into the 
Poser directory, and run it again (as above), I see the splash screen as 
before; and a few more initialization messages than before. But the   
window still disappears. I get the following: 
 
wine: Unhandled exception (thread 0023), starting debugger... 
 
(The debugger doesn't start, I just get dumped back to the command line. 
The thread number changes each time.) 
 
Running 'winedbg Poser.exe' yields the following. (Note that I still 
have MSVCIRT.dll in the program directory. Program behaviour matches the 
previous test.) 
 
WineDbg starting on pid 0x10 
In 32 bit mode. 
0x4048da2c start_process+0xfc 
[/usr/src/packages/wine/wine-20050930/dlls/kernel/../../include/winternl.h:1679] 
in kernel32: jmp 0x4048da1b start_process+0xeb 
[/usr/src/packages/wine/wine-20050930/dlls/kernel/process.c:992] in kernel32 
1679    static inline void WINAPI DbgBreakPoint(void) { __asm__ 
__volatile__("int3"); } 
 
Wine-dbg>cont 
 
First chance exception: page fault on read access to 0x00000044 in 
32-bit code (0x40f48fd6). 
Register dump: 
 CS:0023 SS:002b DS:002b ES:002b FS:1007 GS:0107 
 EIP:40f48fd6 ESP:4063f958 EBP:4063f9b8 EFLAGS:00010246(   - 00 
-RIZP1) 
 EAX:00000000 EBX:40fab384 ECX:00000000 EDX:00000018 
 ESI:00000001 EDI:42c14c50 
Stack dump: 
0x4063f958:  00000000 016003a8 00000000 00000000 
0x4063f968:  00000008 00000000 ffffffff 00000002 
0x4063f978:  00000000 407e9ae0 00000000 42c16308 
0x4063f988:  00000000 00000000 00000008 00000001 
0x4063f998:  00000020 00200001 42e80000 401a62a0 
0x4063f9a8:  407e9680 407e9ae0 4041f6f8 00000018 
0200: sel=1007 base=40016000 limit=00001fff 32-bit rw- 
Backtrace: 
=>1 0x40f48fd6 X11DRV_GetBitmapBits+0x166(hbitmap=0x3298, 
buffer=0x42c16308, count=0x18) 
[/usr/src/packages/wine/wine-20050930/dlls/x11drv/bitmap.c:277] in 
winex11.drv (0x4063f9b8) 
  2 0x40794518 GetBitmapBits+0xb8(hbitmap=0x3298, count=0x20, 
bits=0x42c16308) 
[/usr/src/packages/wine/wine-20050930/dlls/gdi/bitmap.c:341] in gdi32 
(0x4063fa00) 
  3 0x40da63a6 in asi32_12 (+0x463a6) (0x00003298) 
  4 0x00000000 (0x00000000) 
0x40f48fd6 X11DRV_GetBitmapBits+0x166 
[/usr/src/packages/wine/wine-20050930/dlls/x11drv/bitmap.c:277] in 
winex11.drv: call      *0x44(%eax) 
277         XDestroyImage( image ); 
 
Wine-dbg>quit 
 
I'm no programmer, but I can probably get more information from winedbg 
if you need it. 
 
- Cliff 
 

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.