[Bug 32026] New: Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00110025)

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

Bug #: 32026
           Summary: Unhandled exception: page fault on write access to
                    0x00000000 in 32-bit code (0x00110025)
           Product: Wine
           Version: 1.5.13
          Platform: x86
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

Created attachment 42213
  --> http://bugs.winehq.org/attachment.cgi?id=42213
part of wines error report

hi guys i was just trying to open this utility program my friends made 
and it wouldn't run in wine
please see attached file 
hope this is usefull

[Bug 32026] Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00110025)

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

Robert Fairbrother  changed:

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

[Bug 32026] Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00110025)

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

joaopa  changed:

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

--- Comment #1 from joaopa  2012-10-22 02:07:30 CDT ---
Please,
install the latest wine 1.5.15.
install debug symbols.
give a link to download the application.

[Bug 32026] Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00110025)

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

Rosanne DiMesio  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |normal

--- Comment #2 from Rosanne DiMesio  2012-10-22 10:01:25 CDT ---
Not major. http://bugs.winehq.org/page.cgi?id=fields.html#importance
> PE	  400000-  477000	Deferred        facebook account hacker v1.0

Doesn't sound legal.

[Bug 32026] Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00110025)

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

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #3 from Austin English  2012-10-22 13:09:10 CDT ---
WONTFIX.

[Bug 32026] Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00110025)

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

Austin English  changed:

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

--- Comment #4 from Austin English  2012-10-22 18:07:00 CDT ---
Closing.

[Bug 32026] Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00110025)

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

--- Comment #5 from Robert Fairbrother  2012-11-10 14:49:27 CST ---
if you dont have a facebook account or anything to do with those that host it
it there is minimal liability for hacking into an account it all depends on
what software there using and if you wrote the program and how the program
works

*if the program does not officially disclaim that it is ellegal to use how is
the user liable for its use (you could write a game that hacks xboxlive and
plays with the other users and uses it own mock up copy of the game and if it
was distributed officially/commercially yes the guy who wrote it would be in
trouble)

*im in Canada and if you have a program that emits interference with someone
else's communication's resulting in a loss of profit or money technically if
they can prove that then you can be sued but only for the amount they can prove
undeniably that you costed them so like 200.00$ lol unless they can pin whoever
wrote the program witch if they use open source and do not sign there work and
they distribute it out of there jacket pocket for a dollar per copy on the
street good luck finding em lol

the only way to protect your program is to patch it against virulent functions
and require that accounts be accessed by recognized programs eg firefox web
browser otherwise it is a publicly accessible content on a public server open
to receiving and transmitting communications to and from whatever interference
generating device communication with it

[Bug 32026] Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00110025)

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

--- Comment #6 from Robert Fairbrother  2012-11-10 14:50:32 CST ---
i haven't agreed to that because i have never accepted any license agreement
with facebook

[Bug 32026] Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00110025)

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

--- Comment #7 from Robert Fairbrother  2012-11-14 13:32:24 CST ---
fedora does not have the latest version of wine in its mirrors

[Bug 32026] Facebook account hacker v1.0 crashes on startup

https://bugs.winehq.org/show_bug.cgi?id=32026

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
            Summary|Unhandled exception: page   |Facebook account hacker
                   |fault on write access to    |v1.0 crashes on startup
                   |0x00000000 in 32-bit code   |
                   |(0x00110025)                |

--- Comment #8 from Anastasius Focht  ---
Hello folks,

please avoid generic bug summaries in future!
At least mention the application name and version.

It confuses/misleads other users that search for "page fault on write access"
pattern.

Regards