similar to: LoadOEMResource crash [Was: Re: Problem report: SHRINKER.ERR, fix to DEVICE_Open/CreateFileA? ]

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

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

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

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

Hello, capserve.exe is part of Adobe Acrobat 5's PaperCapture plugin. Runnning "wine capserve.exe" I get an error saying "Insufficient memory to perform operation" (although all runs fine under Windows). It seems that several calls to kernel32.VirtualAlloc(), ntdll.NtAllocateVirtualMemory() and related functions are executed right before the error message is issued. See

This was an error I got when running a self-installing executable, power-structure-demo.exe, available from www.write-brain.com (a demo for Power Structure). A error box appears with title SHRINKER.ERR and message: (path)\power-structure-demo.exe (3.4) (time&date) - Pager initialisation error 2 - File not found and then the program quits. Running with --debugmsg

Hi, I was hoping to use wine to run one of those stupid windows binaries that generate a floppy (at least IBM has a clue, and also offers the raw floppy image for dd-ing) In this case, the culprit is seagate's seatools: http://www.seagate.com/support/seatools/ I installed wine under debian unstable (Version: 0.0.20010824-1) and when I run the windows binary under wine, it runs but

The Wine development release 1.5.30 is now available. What's new in this release (see below for details): - Mouse capture support in the Mac driver. - NTLM and Negotiate authentication in WinHTTP. - Support for proxy bypass in WinInet. - Various bug fixes. The source is available from the following locations: http://prdownloads.sourceforge.net/wine/wine-1.5.30.tar.bz2

The system I am using is a clean install of Mandrake 8.0 which has the gcc version 2.96 installed. I downloaded the wine-20010510 snapshot and successfully ran the ./tools/wininstall. The build seems to have run without problems and if I type: wine --version the correct release number is displayed indicating the install was also succesful. As per the FAQ I also did the following:

Hi! I just tried to install an older app from its CD and I've got immediate segfault. When run with --debugmsg +relay, the following was output: (of course just the end of a very long dump) ... 0806ea10:Call x11drv.ShowWindow(00010028,00000005) ret=40715676 0806ea10:Call window proc 0x406e2d90 (hwnd=00010028,msg=WM_SHOWWINDOW,wp=00000001,lp=00000000) 0806ea10:Ret window proc 0x406e2d90

Hi there, I'm relativly new to this linux-stuff an especially to wine. I'm trying to bring up an software that is using the FOXW2600.ESL als runtime library (as far as i understand this). All i can get out of wine is a blank and black (managed) screen an a bunch of messages at starting konsole. At the end wine claims to be successful. I'm running SuSE 7.2 codeweavers-wine-20010305