similar to: VIRTUAL_SetProt and app crashes [Was: Re: LoadOEMResource crash]

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

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, 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

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

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 ) {

I used WinDbg to show the memory protections that were placed on the executable image just after it was loaded, and just before the app starts. Here is what wine shows: View: 0x400000 - 0x765fff 28 0x400000 - 0x765fff c-rw- Here is what WinDbg shows (manually edited to look like the wine view): 0x400000 - 0x400fff c-r-- (PAGE_READONLY) 0x401000 - 0x454fff c--W- (PAGE_WRITECOPY)

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

Here is my thought process on why the application crashes with a protection violation reading a section of memory. I used IDA to disassemble the app. Here's the section where it reads from memory and crashes because of a protection violation: 00760D4A sub_760D4A proc near ; CODE XREF: sub_75FCB0+159^Xp 00760D4A push ebp 00760D4B mov

Hi all, I'm just getting started using WINE. I set it up, and it runs the canonical Solitaire game just fine. My WINE config file is attached. I popped in a Sierra Generations Family Tree Deluxe CD and ran its setup program. A small window titled "Setup" appears with a gas gauge and the text "Generations(R) 4.2 Setup is preparing the InstallShield(R) Wizard which will

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! I have a problem with current wine (from CVS). An application, Dynatext DOC browser from EBT, stopped working. It just opens a dialog box saying that the DYNATEXT.INI file was not found and that it has to be either in the windows directory or in the Dynatext directory. I verified it and it really is in the Dynatext directory, as it used to always be, it's readable and its contents is OK.

The program is Atwin.exe (Accuterm) and going back to the 3.1 version as it's reliance on Windows specific .dll's is better than recent versions... However, I get as far as the initial splash screen and nothing.. If I hit the enter key twice it continues running for a bit, and then hangs.. When I run a trace, I get the following: Can anyone see at a glance if this is a bug, or just a

This is where that 0x761B10 address must have been coming from: 007605E2 sub_7605E2 proc near ; CODE XREF: start+88^Xp 007605E2 mov eax, large fs:0 007605E8 push ebp 007605E9 mov ebp, esp 007605EB push 0FFFFFFFFh 007605ED push 75A010h 007605F2 push 761B10h

On Fri 2018-05-25 10:00:04, Thomas Garnier wrote: > On Fri, May 25, 2018 at 2:14 AM Pavel Machek <pavel at ucw.cz> wrote: > > > On Thu 2018-05-24 09:35:42, Thomas Garnier wrote: > > > On Thu, May 24, 2018 at 4:03 AM Pavel Machek <pavel at ucw.cz> wrote: > > > > > > > On Wed 2018-05-23 12:54:03, Thomas Garnier wrote: > > > > >

On Fri, May 25, 2018 at 2:14 AM Pavel Machek <pavel at ucw.cz> wrote: > On Thu 2018-05-24 09:35:42, Thomas Garnier wrote: > > On Thu, May 24, 2018 at 4:03 AM Pavel Machek <pavel at ucw.cz> wrote: > > > > > On Wed 2018-05-23 12:54:03, Thomas Garnier wrote: > > > > Change the assembly code to use only relative references of symbols for > > the

Really? Me? Oh Pavel! I would be inestimably honoured. On 04/27/2012 01:55 AM, Pavel Ismailov wrote: > Hello! > > My name is Pavel Ismailov > and I`m CEO of www.flashphoner.com project. > > We noticed that you quite active in Asterisk-user > mail list, and would like to offer you buy signature > in your messages for some monthly price. > > Is it interested for

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's been a while since our last release and Shirish's new cifs.idmap utility has now been merged. The last release was 4.9, so I've been a bit torn -- should I call this one 4.10 or 5.0? Then I figured...when in doubt, copy Linus. Since he just bumped the major version number of the kernel, this is now version 5.0. The main changes: -

On Thu 2018-05-24 09:35:42, Thomas Garnier wrote: > On Thu, May 24, 2018 at 4:03 AM Pavel Machek <pavel at ucw.cz> wrote: > > > On Wed 2018-05-23 12:54:03, Thomas Garnier wrote: > > > Change the assembly code to use only relative references of symbols for > the > > > kernel to be PIE compatible. > > > > > > Position Independent Executable

On Thu 2018-05-24 09:35:42, Thomas Garnier wrote: > On Thu, May 24, 2018 at 4:03 AM Pavel Machek <pavel at ucw.cz> wrote: > > > On Wed 2018-05-23 12:54:03, Thomas Garnier wrote: > > > Change the assembly code to use only relative references of symbols for > the > > > kernel to be PIE compatible. > > > > > > Position Independent Executable

Hi all, Just getting started with LLVM, and trying to write a back end for a toy hypothetical processor. I'm using llvm-gcc with -emit-llvm to see the LLVM code. The LLVM code is very well-documented at http://llvm.org/docs/LangRef.html. However, I'm looking for equivalent documentation for SelectionDAGs. As I understand it, instructions in the target specification get matched against the