[Bug 9742] New: EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

Summary: EngineSite segfaults (Segmentation fault)
           Product: Wine
           Version: unspecified
          Platform: PC
               URL: http://luckasoft.com/download/perle_le.exe
        OS/Version: Linux
            Status: UNCONFIRMED
          Keywords: regression
          Severity: normal
          Priority: P2
         Component: wine-gdi-(printing)
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

A user reported trouble with this app in this thread: 
http://groups.google.nl/group/comp.emulators.ms-windows.wine/browse_thread/t...

I tried it , and it just segfaults after the splash screen. However , in
wine-0.9.2 it gets nicely beyond the spash screen, and seems to start fine.
I'll put some more info into this bug later on

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

--- Comment #1 from Louis Lenders   2007-09-23 12:01:45 ---
A regression test showed that the app stopped working after this patch:
http://www.winehq.org/pipermail/wine-cvs/2006-March/021611.html

However, when i revert that patch, the app still segfaults. I tried play a
little bit with the fonts, but i can't get the app working. Also, i find it a
bit strange that this patch could make an application crash, but i'm pretty
sure i did the regression test correctly. So rather stuck now :(

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Austin English   2007-09-23 19:43:36 ---
I tried to verify your results, but I can't build it (too old). Have you tried
testing the parent commit to see if it works there?

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

Lei Zhang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
           Keywords|                            |download

--- Comment #3 from Lei Zhang   2007-10-09 13:52:09 ---
louis confirmed the original reporter's problem.

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

--- Comment #4 from Timo-Heikki Mäkelä   2008-03-12 13:16:25 ---
Created an attachment (id=11339)
 --> (http://bugs.winehq.org/attachment.cgi?id=11339)
console output

I'm not sure, if I got the same problem on 0.9.57, but launching the program it
sure did fault after the logo and the logo became a zombie process. When
running the program again through console, I got this output on the screen.
Also my browser went down while the program was running.

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

--- Comment #5 from Timo-Heikki Mäkelä   2008-03-12 13:18:14 ---
Created an attachment (id=11340)
 --> (http://bugs.winehq.org/attachment.cgi?id=11340)
The zombie logo

Here's a screenshot showing the zombie process on top of console output.

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

Lei Zhang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #11339|application/octet-stream    |text/plain
          mime type|                            |

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #6 from Anastasius Focht   2008-03-12 16:18:41 ---
Hello,

the app contains brain damaged code which conflicts with wine's handling of
DIBs.
Another case of ESP being abused while accessing DIB regions (see
http://bugs.winehq.org/show_bug.cgi?id=10503 for similar problem).

With the current DIB handling, wine can't recover from X11DRV_DIB_FaultHandler
if the fault was raised while ESP being abused.

--- snip brain damage ---
push    ebp
mov     ebp, esp
..
mov     ds:esp_save, esp
mov     ds:ebp_save, ebp
..
mov     esp, esi
mov     ecx, ecx
mov     eax, [ebp]
mov     edi, [esp]
mov     ebx, eax
and     eax, 0FF00FF00h
and     ebx, 0FF00FFh
..
mov     esp, ds:esp_save
mov     ebp, ds:ebp_save
pop     ebp
..
--- snip brain damage ---

Ask Jesse Allen or whoever is working on the new DIB code for timeline of
getting the engine into official wine tree ...

Regards

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |421

--- Comment #7 from Austin English   2008-12-05 03:08:23 ---
Still present in git.

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

--- Comment #8 from Anastasius Focht   2009-01-17 06:44:50 ---
Hello,

how about merging all segfault-by-stack-pointer-abuse bugs due to Wine's
current DIB implementation into one and closing dupes?
The issue is well known - no need to keep separate bug reports.

Regards

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

Adys  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adys.wh+winehqdotorg@gmail.
                   |                            |com

--- Comment #9 from Adys   2009-06-07 10:20:08 ---
(In reply to comment #8)
> Hello,
>
> how about merging all segfault-by-stack-pointer-abuse bugs due to Wine's
> current DIB implementation into one and closing dupes?
> The issue is well known - no need to keep separate bug reports.
>
> Regards

Is this fixed by Max's (or another) DIB engine implementation? If so, it could
be made a dupe of bug 421.

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

--- Comment #10 from Anastasius Focht   2010-01-03 07:06:38 ---
Hello,

revisiting. Obviously still present with wine-1.1.35

--- quote ---
Is this fixed by Max's (or another) DIB engine implementation? If so, it could
be made a dupe of bug 421.
--- quote ---

Most likely.
Again: merge app bugs with DIB + ESP abuse into one (depend on bug 421 -> new
DIB engine).

For example mark this one a dupe of bug 10503 (because there is more
discussion/info/proof in bug 10503).

Regards

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #11 from Austin English   2010-01-03 13:12:38 ---
Dupe, per Anastasius.

*** This bug has been marked as a duplicate of bug 10503 ***

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #12 from Dmitry Timoshkov   2010-01-04 00:02:38 ---
Closing duplicate.

[Bug 9742] EngineSite segfaults (Segmentation fault)

http://bugs.winehq.org/show_bug.cgi?id=9742

Bug 9742 depends on bug 421, which changed state.

Bug 421 Summary: Implement a DIB engine
http://bugs.winehq.org/show_bug.cgi?id=421

What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED