Andreas Mohr a.mohr@mailto.de writes:
Call msvcrt.mktime(405b614c) ret=5f40e3b3 tid=08066638 Ret msvcrt.mktime() retval=3adae6b2 ret=5f40e3b3 tid=08066638 trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=c0000005 flags=0 Call ntdll.RtlRaiseException(404a4aa8) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1
80000100 is EXCEPTION_WINE_STUB; the app probably called a stub from the exception handler of the first seg fault (and then called the same stub from the handler of the stub exception, etc.) The debugger should be able to tell you more about it.
On Mon, Apr 16, 2001 at 02:28:00PM -0700, Alexandre Julliard wrote:
Andreas Mohr a.mohr@mailto.de writes:
Call msvcrt.mktime(405b614c) ret=5f40e3b3 tid=08066638 Ret msvcrt.mktime() retval=3adae6b2 ret=5f40e3b3 tid=08066638 trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=c0000005 flags=0 Call ntdll.RtlRaiseException(404a4aa8) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1
80000100 is EXCEPTION_WINE_STUB; the app probably called a stub from the exception handler of the first seg fault (and then called the same stub from the handler of the stub exception, etc.) The debugger should be able to tell you more about it.
Err, which debugger ??
I get "Segmentation fault", and that's it...
On 16 Apr 2001, Alexandre Julliard wrote:
Andreas Mohr a.mohr@mailto.de writes:
Call msvcrt.mktime(405b614c) ret=5f40e3b3 tid=08066638 Ret msvcrt.mktime() retval=3adae6b2 ret=5f40e3b3 tid=08066638 trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=c0000005 flags=0 Call ntdll.RtlRaiseException(404a4aa8) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1
80000100 is EXCEPTION_WINE_STUB; the app probably called a stub from the exception handler of the first seg fault (and then called the same stub from the handler of the stub exception, etc.) The debugger should be able to tell you more about it.
Yes, it's trying to call msvcrt.__CxxFrameHandler, and the first exception is because it was trying to access 0x80b4c4d8 and that does not seem very normal.
09420d38:trace:seh:EXC_RtlRaiseException Unhandled page fault on write access to 0x80b4c4d8 at address 0x0804ff6e. ... 09420d38:err:seh:EXC_RtlRaiseException Unimplemented function msvcrt.__CxxFrameHandler called at address 0x4005c443.
Also I had lost of trouble running mspaint when using the builtin msvcrt. None of the following works: $ wine /mnt/win98/Program\ Files/Accessories/mspaint.exe $ wine "/mnt/win98/Program Files/Accessories/mspaint.exe" $ wine "c:/Program Files/Accessories/mspaint.exe" $ wine "c:\Program Files\Accessories\mspaint.exe"
They all tell me that 'H:\wine\Files\Accessories\mspaint.exe was not found.'. If I use native msvcrt they all work (and wine is the real thing, not a script).
-- Francois Gouget fgouget@free.fr http://fgouget.free.fr/ "Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)" -- Linus Torvalds
-
Alexandre Julliard -
Andreas Mohr -
Francois Gouget