search for: pe_resourc

Displaying 3 results from an estimated 3 matches for "pe_resourc".

Did you mean: pe_resource
2001 Dec 08
1
LoadOEMResource crash [Was: Re: Problem report: SHRINKER.ERR, fix to DEVICE_Open/CreateFileA? ]
...c_trapno = 14, sc_err = 4, sc_eip = 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=0x...
2002 Oct 05
6
Problems with installing
.../dos_fs.c ../../files/drive.c ../../files/file.c ../../files/profile.c ../../files/smb.c ../../files/tape.c ../../if1632/builtin.c ../../if1632/relay.c ../../if1632/snoop.c ../../loader/elf.c ../../loader/loadorder.c ../../loader/main.c ../../loader/module.c ../../loader/pe_image.c ../../loader/pe_resource.c ../../loader/resource.c ../../loader/task.c ../../loader/ne/convert.c ../../loader/ne/module.c ../../loader/ne/resource.c ../../loader/ne/segment.c ../../memory/atom.c ../../memory/codepage.c ../../memory/environ.c ../../memory/global.c ../../memory/heap.c ../../memory/instr.c ../../memory/...
2001 Dec 08
1
LoadOEMResource crash [Was: Re: Problem report: SHRINKER.ERR, fix to DEVICE_Open/CreateFileA? ]
...00714d0 code=c0000005 flags=0 0806d398:trace:seh:EXC_RtlUnwind code=c0000005 flags=2 0806d398:trace:seh:EXC_CallHandler calling handler at 0x40070d60 code=c0000005 flags=2 0806d398:trace:seh:EXC_CallHandler handler returned 1 0806d398:warn:resource:RES_FindResource page fault This time eip is in pe_resource.c in libntdll.so, the find_entry_by_id method. The exception is handled by NTDLL.DLL.__wine_exception_handler in libntdll.so. Finally, about 2000 lines later, our friend the LoadOEMResource exception occurs. So we have three exceptions in a row. The first is apparently intercepted by the app...