search for: res_loadresourc

Hi Pavel, Right, my app also crashes in a different place under winedbg, although it crashes in the same winedbg place under gdb. I took a closer look at wine --winver nt40 --debugmsg +all. I found something interesting. If I search for queue_exception, I find that there is an exception raised before the LoadOEMCall, about 328klines in: 0806d398:Call

Howdy, Running a FPGA design tool (Actel's Designer), I find that it works pretty good, but that certain printed status strings are being formatted incorrectly. It does not seem to affect the operation of the application, except for the status reports. For example, running wine --debugmsg +text,+string,+win /d/Actel/bin/designer and opening an existing design gives this:

...493 0806d388:trace:resource:FormatMessageA (0x1000,(nil),2,0x400,0x75d54b,200,(nil))0806d388:trace:resource:load_messageA instance = 40667000, id = 00000002, buffer = (nil), length = 100 0806d388:trace:resource:RES_FindResource2 (40667000, 0000000b, 00000001, 0400, W, PE) 0806d388:trace:resource:RES_LoadResource (40667000, 406ac8c0, PE) 0806d388:trace:resource:LockResource (406974e0) 0806d388:trace:resource:load_messageA - strlen=20 0806d388:trace:heap:HeapAlloc (403b0000,00000002,00000018): returning 4042ef68 0806d388:trace:resource:load_messageA instance = 40667000, id = 00000002, buffer = 0x4042ef6...