>Here is the backtrace from regular gdb: > >#0 0x00000000 in ?? () >#1 0x400be693 in EXC_CallHandler (record=0x40691c10, frame=0x40691d80, >context=0x406918ac, dispatcher=0x40691848, > handler=0, nested_handler=0x400be5d0 <EXC_RaiseHandler>) at exception.c:117 >#2 0x400be9b9 in EXC_RtlRaiseException (rec=0x40691c10, context=0x406918ac) at >exception.c:213 >#3 0x400cdd99 in __wine_call_from_32_regs () from /usr/local/lib/libntdll.dll.so >#4 0x400be8b5 in RtlRaiseException () from /usr/local/lib/libntdll.dll.so >#5 0x40aa31ec in __wine_stub_rpcrt4_dll_314 () at rpcrt4.spec.c:356 >#6 0x788f6974 in ?? () >#7 0x788f31b8 in ?? () >#8 0x788f5a65 in ?? () >#9 0x7ca0ac41 in ?? () >#10 0x7ca09194 in ?? () >#11 0x4091640f in CryptAcquireContextA (phProv=0x40691f60, pszContainer=0x1502b5f0 >"Blizzard_Storm", > pszProvider=0x1502b600 "Microsoft Base Cryptographic Provider v1.0", >dwProvType=1, dwFlags=8) at crypt.c:332 >#12 0x1500f568 in ?? ()
Maybe it's looking for function 314 in rpcrt4.dll which seems to be a stub and therefore it fails. But I don't know why winedbg behaves strangely. bye Fabi
