Paul Vriens a écrit :
Eric Pouech wrote:
Kapila De Silva a écrit :
Hi All,
Im trying to debug a crash in Everquest 2, (bug 7705) and am hoping
someone here can help.
I'll send a fix later on for the FIXME, but it's unlikely this is
what's causing the crash
So, you have to understand where the 0xffffffff as an address comes
from. sometimes, +relay helps figuring that out, but YMMV
A+
Hi,
just wanted to report that Process Explorer also calls it with
0xffffffff when viewing the 'System Information':
trace:dbghelp:SymInitializeW (0xffffffff (null) 0)
trace:dbghelp:elf_load_file Processing elf file 'L"wine-kthread"' at
00000000
trace:dbghelp:elf_load_file Processing elf file
'L"/usr/lib/qt-3.3/bin/wine-kthread"' at 00000000
trace:dbghelp:elf_load_file Processing elf file
'L"/usr/kerberos/bin/wine-kthread"' at 00000000
trace:dbghelp:elf_load_file Processing elf file
'L"/usr/local/bin/wine-kthread"' at 00000000
Could 0xffffffff mean something like system-wide?
Cheers,
Paul.
in that cas 0xffffffff is the default handle to the current process, and
is never derefenced...
include/winbase.h:#define GetCurrentProcess() ((HANDLE)0xffffffff)
A+
--
Eric Pouech
"The problem with designing something completely foolproof is to underestimate the
ingenuity of a complete idiot." (Douglas Adams)