Displaying 2 results from an estimated 2 matches for "find_entry_by_namew".
2001 Dec 08
1
LoadOEMResource crash [Was: Re: Problem report: SHRINKER.ERR, fix to DEVICE_Open/CreateFileA? ]
...return NULL;
}
Where the offending line is
min = dir->NumberOfNamedEntries;
It looks like the call was made with dir = 0x0045F000, id = 0xE, and I'm
not sure about root.
Probably find_entry_by_id was called from either PE_FindResourceW or
PE_FindResourceExW, possibly through find_entry_by_nameW, which was
called by RES_FindResource2, which is the last trace before the exception.
If I could get winedbg/gdb to continue past the first exception but stop
at the second, I might be able to find out more :(
--Rob
2001 Dec 08
1
LoadOEMResource crash [Was: Re: Problem report: SHRINKER.ERR, fix to DEVICE_Open/CreateFileA? ]
...1074344288, sc_cs = 35, __csh = 0, sc_eflags = 66050, esp_at_signal =
1078935700, sc_ss = 43, __ssh = 0, i387 = 0, oldmask = 0, cr2 =
4583436}) at signal_i386.c:882
#3 <signal handler called>
#4 find_entry_by_id (dir=0x45f000, id=14, root=0x45f000) at
pe_resource.c:83
#5 0x4009322e in find_entry_by_nameW (dir=0x45f000, name=0xe,
root=0x45f000)
at pe_resource.c:115
#6 0x400934b4 in PE_FindResourceW (hmod=4194304, name=0x4074c30e, type=0xe)
at pe_resource.c:239
#7 0x40094083 in RES_FindResource2 (hModule=4194304, type=0xe "",
name=0x4074c30e "",
lang=0, bUnicode...