w2k Explorer makes wine crash in RtlRaiseException [Virus checked]
Hello On my Suse 7.3 Linux (Kernel 2.4.4) I tried to start the w2k Explorer (Version 5.0 (Build 2195: Service Pack 3) using wine-20030115 with just buildin dlls. tm(a)penguin:~/c/w2k > winedbg explorer For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_AT - 0C07; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_AT - 0C07; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE fixme:console:SetConsoleCtrlHandler (0x404c3340,1) - no error checking or testing yet For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_AT - 0C07; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE fixme:shell:SHLWAPI_437 (0x00000004) stub fixme:process:SetProcessShutdownParameters (00000002, 00000000): partial stub. fixme:shell:FileIconInit (true) fixme:ntdll:NtOpenProcessToken (0xffffffff,0x00000008,0x406b2e08): stub fixme:ntdll:NtQueryInformationToken (0xcafe,10,0x406b2dc4,56,0x406b2dfc): stub Copied by hand from the winedbg window: 0011: sel=008f base=401145e0 limit=00000fff 32-bit rw- Backtrace: =>0 0x400c3de5 (RaiseException+0x75(code=0xc06d007f, flags=0x0, nbargs=0x1, args=0x406b2df8) [except.c:84] in libntdll.dll.so) (ebp=406b2da8) 1 0x0040de7f (explorer.exe.EntryPoint+0xc8d7 in C:\w2k\explorer.exe) (ebp=406b2df0) 2 0x0040a30f (explorer.exe.EntryPoint+0x8d67 in C:\w2k\explorer.exe) (ebp=406b2e3c) 3 0x00401621 (explorer.exe.EntryPoint+0x79 in C:\w2k\explorer.exe) (ebp=406b2e9c) 4 0x400ba038 (start_process+0x248 [process.c:564] in libntdll.dll.so) (ebp=406b2f38) 5 0x400beb3d (call_on_thread_stack+0x1d(func=0x400b9df0) [sysdeps.c112] in libntdll.dll.so) (ebp=406b2ff4) 6 0x400bece4 (SYSDEPS_CallOnStack+0x14 in libntdll.dll.so) (ebp=00000000) 0x400c3de5 (RaiseException+0x75 [except.c84] in libntdll.dll.so): leal 0xffffffa8(%ebp),%esp 84 RtlRaiseException( &record ); This seems to be an error in the wine exception handling. Is this right? What can be done about that? Greetings Thomas Mertes
*please* dont run explorer at all --- thomas.mertes(a)t-mobile.at a écrit : > Hello
On my Suse 7.3 Linux (Kernel 2.4.4) I tried to start the w2k Explorer (Version 5.0 (Build 2195: Service Pack 3) using wine-20030115 with just buildin dlls.
tm(a)penguin:~/c/w2k > winedbg explorer For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_AT - 0C07; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_AT - 0C07; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE fixme:console:SetConsoleCtrlHandler (0x404c3340,1) - no error checking or testing yet For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_AT - 0C07; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE fixme:shell:SHLWAPI_437 (0x00000004) stub fixme:process:SetProcessShutdownParameters (00000002, 00000000): partial stub. fixme:shell:FileIconInit (true) fixme:ntdll:NtOpenProcessToken (0xffffffff,0x00000008,0x406b2e08): stub fixme:ntdll:NtQueryInformationToken (0xcafe,10,0x406b2dc4,56,0x406b2dfc): stub
Copied by hand from the winedbg window: 0011: sel=008f base=401145e0 limit=00000fff 32-bit rw- Backtrace: =>0 0x400c3de5 (RaiseException+0x75(code=0xc06d007f, flags=0x0, nbargs=0x1, args=0x406b2df8) [except.c:84] in libntdll.dll.so) (ebp=406b2da8) 1 0x0040de7f (explorer.exe.EntryPoint+0xc8d7 in C:\w2k\explorer.exe) (ebp=406b2df0) 2 0x0040a30f (explorer.exe.EntryPoint+0x8d67 in C:\w2k\explorer.exe) (ebp=406b2e3c) 3 0x00401621 (explorer.exe.EntryPoint+0x79 in C:\w2k\explorer.exe) (ebp=406b2e9c) 4 0x400ba038 (start_process+0x248 [process.c:564] in libntdll.dll.so) (ebp=406b2f38) 5 0x400beb3d (call_on_thread_stack+0x1d(func=0x400b9df0) [sysdeps.c112] in libntdll.dll.so) (ebp=406b2ff4) 6 0x400bece4 (SYSDEPS_CallOnStack+0x14 in libntdll.dll.so) (ebp=00000000)
0x400c3de5 (RaiseException+0x75 [except.c84] in libntdll.dll.so): leal 0xffffffa8(%ebp),%esp 84 RtlRaiseException( &record );
This seems to be an error in the wine exception handling. Is this right? What can be done about that?
Greetings Thomas Mertes
===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus, in "Matrix". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Sylvain Petreolle wrote:
--- thomas.mertes(a)t-mobile.at a écrit : > Hello
On my Suse 7.3 Linux (Kernel 2.4.4) I tried to start the w2k Explorer (Version 5.0 (Build 2195: Service Pack 3) using wine-20030115 with just buildin dlls.
*please* dont run explorer at all
*please* dont run explorer at all
$$$!!!.&&&. Well sure you can run explorer but you should be aware that this dainbread program likes to trash the windows system directory. The reason for this is seems to be related to missing entries in the registry files. There is a fixup program that might repair the damage (it usualy does). I don't care about my windows install. The only time I use it is to test a programs behavior under windows. Anyway debugging this behavior has been a PITA and I personally have made little headway when I have tried to debug it. By the same token it would be nice not to have it do the damage it does. Apparently you can get this corruption even if you dont run explorer directly since some programs (like msn) will call explorer.exe. FWIW This is in the README. -- Tony Lambregts
why dont we apply the patch for the implementation of explorer.exe proposed by Dan Kegel ? It would stop all reports like this. http://www.winehq.com/hypermail/wine-devel/2003/01/0768.html
Apparently you can get this corruption even if you dont run explorer directly since some programs (like msn) will call explorer.exe.
FWIW This is in the README.
--
Tony Lambregts
===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus, in "Matrix". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Sylvain Petreolle wrote:
why dont we apply the patch for the implementation of explorer.exe proposed by Dan Kegel ? It would stop all reports like this.
http://www.winehq.com/hypermail/wine-devel/2003/01/0768.html
Well this patch is for a fake windows install AFAICT a fake windows install does not have this problem. The problem is when you use "wine with windows" install -- Tony Lambregts
Sylvain Petreolle wrote:
Apparently you can get this corruption even if you dont run explorer directly since some programs (like msn) will call explorer.exe.
why dont we apply the patch for the implementation of explorer.exe proposed by Dan Kegel ? It would stop all reports like this.
http://www.winehq.com/hypermail/wine-devel/2003/01/0768.html
If MSN is calling explorer, maybe we should apply the patch regardless of the bug reports. It'd be nice if MSN was closer to working on fake windows. BTW, my patch only implements one commandline parameter, a directory name. Anyone know if MSN or any other common program uses any of the other options the real explorer.exe offers? Maybe I should update my patch so the fake explorer aborts if you use an unrecognized option. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
If MSN is calling explorer, maybe we should apply the patch regardless of the bug reports. It'd be nice if MSN was closer to working on fake windows.
BTW, my patch only implements one commandline parameter, a directory name. Anyone know if MSN or any other common program uses any of the other options the real explorer.exe offers?
Better : return with sucessfull state to programs that calls it, display a msgbox with all arguments and a message to report this on the list.
Maybe I should update my patch so the fake explorer aborts if you use an unrecognized option. - Dan
===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus, in "Matrix". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
participants (4)
-
Dan Kegel -
Sylvain Petreolle -
thomas.mertes＠t-mobile.at -
Tony Lambregts