search for: loadoemresource

Hi Pavel, Can you run your app under winedbg? When I run my app under winedbg, it segfaults inside the application code with a bad read access. The specific instruction it faults on is movl 0x10(%esi),%eax (aka mov [esi+0x10],eax for IDA users). I'm curious to know if your app uses the same library as mine... --Rob

...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 application. The second is generated by trying to display the message box popped up by the first exception. The third is generated in LoadOEMResource, *probably* long after the application was s...

More information on exception #2. The offending function is: /********************************************************************** * find_entry_by_id * * Find an entry by id in a resource directory */ static const IMAGE_RESOURCE_DIRECTORY *find_entry_by_id( const IMAGE_RESOURCE_DIRECTORY *dir, WORD id, const void *root ) {

Hmm. I'm just throwing this out there. Maybe the problem will always happen when the application wants to catch an exception but wine catches it instead, and then some internal data structures get trashed when the app resumes? --Rob

Oh, I think I see now. There was a call to VIRTUAL_SetProt, which protected memory mapped regions of memory, before the first exception: 0806d398:trace:virtual:VIRTUAL_SetProt 0x459000-0x459fff c-r-- View: 0x400000 - 0x765fff 28 0x400000 - 0x400fff c-r-- 0x401000 - 0x458fff c---- 0x459000 - 0x459fff c-r-- 0x45a000 - 0x758fff c---- 0x759000 - 0x765fff c-rw- And

Interesting. In my app, the first exception appears to occur because the app tries to read memory at 0x456010 from a segment that had been declared c---- by a previous call to VIRTUAL_VirtProt. Pavel, I'm willing to bet your error is the same. So what gives? --Rob

Hooray, I got gdb to do what I need, to skip the first exception and break before the second. The key commands are: gdb (winepath)/bin/wine Set the arguments: > set args --winver nt40 yourapp Tell gdb to pass segmentation faults to the program: > handle SIGSEGV nostop pass Set a breakpoint at main: > b main Run the program: > run This loads all the shared libraries, and

...08067f18:Call PE DLL (proc=0x40692430,module=4067f000,type=1,res=0x1) 08067f18:Call PE DLL (proc=0x409ba0e0,module=409b3000,type=1,res=(nil)) 084a06c0:Starting thread (entryproc=0x400db1e0) 08067f18:Ret PE DLL (proc=0x409ba0e0,module=409b3000,type=1,res=(nil)) retval=108067f18:Call x11drv.LoadOEMResource(00007fe3,00000001) ret=406c3739 fixme:x11drv:OBM_CreateBitmaps Xpm support not in the binary, please install the Xpm and Xpm-devel packages and recompile 08067f18:Ret x11drv.LoadOEMResource() retval=00000000 ret=406c3739 08067f18:Call x11drv.LoadOEMResource(00007fed,00000001) ret=406c3739...

...ow proc 0x406c1dbc (hwnd=00010029,msg=WM_NCCALCSIZE,wp=00000000,lp=404d41d8) 0806ea10:Ret window proc 0x406c1dbc (hwnd=00010029,msg=WM_NCCALCSIZE,wp=00000000,lp=404d41d8) retval=00000300 0806ea10:Call window proc 0x406c1dbc (hwnd=00010029,msg=WM_CREATE,wp=00000000,lp=404d4554) 0806ea10:Call x11drv.LoadOEMResource(00007ff7,00000001) ret=406eddb2 Segmentation fault When I added +file,+dosfs, there was no difference in this part, so I think there are no file operations involved. Please note that although there were many window operations before the crash, there was no window visible on the screen. I don'...

...section 0x40687290 wait timed out, retrying (60 sec) fs=01e7 Wine exited with a successful status Any ideas ? (please) Any more log I can provide ? (wine -debugmsg +all is 2,5 MB and doesn *not* end up with the RtlpWaitForCriticalSection error, but <snip approx.2 MB> Call x11drv.17: LoadOEMResource(00007ff7,00000001) ret=40633dbe fs=02d7 trace:heap:HeapAlloc (40340000,00000002,0000008c): returning 403e75d8 trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 0810d2a8: queue_exception_event( first=1, record={context={flags=00000000,eax=40c01e90,ebx=407bf0e0,ecx=403bdc40,e dx=00000000,esi=40c...