http://bugs.winehq.org/show_bug.cgi?id=4663
------- Additional Comments From multescugeorge@yahoo.com 2006-16-03 04:51 ------- I'm new at debugging things, but perhaps someone can use this info:
winedbg /.wine/drive_c/Program\ Files/YPOPs/ypops.exe WineDbg starting on pid 0x36 start_process () at /usr/src/wine/dlls/kernel/process.c:845 0x7fca111f start_process+0xb7 [/usr/src/wine/dlls/kernel/process.c:845] in kernel32: subl $12,%esp 845 ExitProcess( entry( peb ) ); Wine-dbg>stepi 7620 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x7fca1123 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x46df42 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x471006 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x470ecc fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x470be0 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x470be8 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x470bf0 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x470bf8 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x470972 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x46d65d fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x47099a fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x4709ab fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x46d7c9 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x4742f3 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x474401 fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0x10) at 0x47440f wine_server_handle_to_fd () at /usr/src/wine/dlls/ntdll/server.c:492 0x7ffb6747 wine_server_handle_to_fd+0xff [/usr/src/wine/dlls/ntdll/server.c:492] in ntdll: xorl %eax,%eax 492 SERVER_START_REQ( get_handle_fd ) Wine-dbg>stepi 100 0x4991c078 write+0x8 in libpthread.so.0: jnz 0x4991c09c write+0x2c in libpthread.so.0 Wine-dbg>stepi 0x4991c07a write+0xa in libpthread.so.0: pushl %ebx Wine-dbg>stepi 0x4991c07b write+0xb in libpthread.so.0: movl 0x10(%esp),%edx Wine-dbg>stepi 0x4991c07f write+0xf in libpthread.so.0: movl 0xc(%esp),%ecx Wine-dbg>stepi 0x4991c083 write+0x13 in libpthread.so.0: movl 0x8(%esp),%ebx Wine-dbg>stepi 0x4991c087 write+0x17 in libpthread.so.0: movl $0x4,%eax Wine-dbg>stepi 0x4991c08c write+0x1c in libpthread.so.0: call *%gs:0x00000010 Wine-dbg>stepi 0xffffe400: pushl %ecx Wine-dbg>stepi 0xffffe401: pushl %edx Wine-dbg>stepi 0xffffe402: pushl %ebp Wine-dbg>stepi 0xffffe403: movl %esp,%ebp Wine-dbg>stepi 0xffffe405: sysenter Wine-dbg>stepi err:seh:raise_exception Unhandled exception code 80000003 flags 0 addr 0xffffe410 0xffffe410: -- no code accessible -- Wine-dbg>bt Backtrace:
Exception c0000005 Wine-dbg>list 492 SERVER_START_REQ( get_handle_fd ) 493 { 494 req->handle = handle; 495 req->access = access; 496 if (!(ret = wine_server_call( req ))) 497 { 498 fd = reply->fd; 499 removable = reply->removable; 500 if (flags) *flags = reply->flags; 501 } 502 } Wine-dbg>info exception Exception frames: Can't read TEB:except_frame Wine-dbg>info wnd Window handle Class Name Style WndProc Thread Text 00050020 #32769 96000000 00000000 00000039 -- Empty -- 00050022 Shell_TrayWnd 04c00000 00000000 00000039 Wine Systray L Wine-dbg>info regs Register dump: CS:0073 SS:007b DS:007b ES:007b FS:1007 GS:0033 EIP:ffffe410 ESP:7fa2fb5c EBP:7fa2fc4c EFLAGS:00200246( - 00 - IZP1) EAX:00000040 EBX:00000003 ECX:7fa2fc7c EDX:00000040 ESI:00000004 EDI:00000000 Wine-dbg>stepi Cannot set ctx on 55 Process of pid=0x00000036 has terminated
**************************************************************** at least i got some indication of an error, if i run program with wine i only get carige return. Seems systray if sabotaged by wine-server, or wine-server can't latch on to the handle, i'm confused.