[Bug 22913] New: winedbg: __pthread_mutex_lock_full: Assertion `robust || (oldval & 0x40000000) == 0' failed.

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

Summary: winedbg: __pthread_mutex_lock_full: Assertion `robust
                    || (oldval & 0x40000000) == 0' failed.
           Product: Wine
           Version: 1.2-rc1
          Platform: x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

As discussed on IRC, filing for prosperity. WoW crashes, winedbg subsequently
complains about a pthread assertion error.

wine: Unhandled exception 0xc0000409 at address 0x1c33ebd (thread 0030),
starting debugger...
pthread_mutex_lock.c:321: __pthread_mutex_lock_full: Assertion `robust ||
(oldval & 0x40000000) == 0' failed.
Segmentation fault
Process of pid=002f has terminated
No process loaded, cannot execute 'echo Modules:'
Cannot get info on module while no process is loaded
No process loaded, cannot execute 'echo Threads:'
process  tid      prio (all id:s are in hex)
0000000e services.exe
        00000014    0
        00000010    0
        0000000f    0
00000011 winedevice.exe
        00000017    0
        00000013    0
        00000012    0
00000018 explorer.exe
        00000019    0
You must be attached to a process to run this command.
No process loaded, cannot execute 'detach'

[Bug 22913] winedbg: __pthread_mutex_lock_full: Assertion `robust || (oldval & 0x40000000) == 0' failed.

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

Paul Chitescu  changed:

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

--- Comment #1 from Paul Chitescu   2010-05-28 06:27:39 ---
Exception 0xc0000409 is STATUS_STACK_BUFFER_OVERRUN so probably the memory was
corrupted by runaway code leading to an invalid pthread mutex structure.

[Bug 22913] WoW crashes

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

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|winedbg:                    |WoW crashes
                   |__pthread_mutex_lock_full:  |
                   |Assertion `robust ||        |
                   |(oldval & 0x40000000) == 0' |
                   |failed.                     |

--- Comment #2 from Dmitry Timoshkov   2010-05-28 06:30:26 ---
Assertion is probably a glibc bug. Do you run WoW with -opengl?

[Bug 22913] WoW crashes

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

--- Comment #3 from Jerome Leclanche   2010-05-28 06:35:29 ---
(In reply to comment #2)
> Assertion is probably a glibc bug. Do you run WoW with -opengl?

The wow crash is an application crash, not a wine bug; the bug here is
apparently winedbg shouldn't fire in this specific case. This is out of my
league but here's a quick log:

[12:14:47] <killall-9> STATUS_STACK_BUFFER_OVERRUN
[12:15:23] <killall-9> some errors should just kill the process as it's
impossible to recover
[12:15:45] <killall-9> cannot debug a stack overflow
[12:17:01] <killall-9> yeah
[12:17:14] <killall-9> wine shouldn't try to fire winedbg at all
[12:17:20] * Adys nods
[12:17:30] <Adys> display a relevant error i guess
[12:17:42] <@puk> core dump

[Bug 22913] winedbg is inappropriately called on some exceptions.

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

Jerome Leclanche  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|WoW crashes                 |winedbg is inappropriately
                   |                            |called on some exceptions.

--- Comment #4 from Jerome Leclanche   2010-05-29 04:41:28 ---
(Changing title to reflect the issue is *not* related to wow)

[Bug 22913] winedbg is inappropriately called on some exceptions.

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

--- Comment #5 from Alexandre Julliard   2010-05-29 05:22:01 ---
winedbg fires on unhandled exceptions. Sometimes the process state is too
corrupted to allow proper debugging, but that doesn't mean winedbg shouldn't
start. The real problem is why there is an unhandled exception in the first
place.

[Bug 22913] winedbg is inappropriately called on some exceptions.

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

Alexandre Julliard  changed:

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

--- Comment #6 from Alexandre Julliard   2010-05-29 10:41:26 ---
Apparently crashes on Windows too.

[Bug 22913] winedbg is inappropriately called on some exceptions.

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

Vitaliy Margolen  changed:

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

--- Comment #7 from Vitaliy Margolen   2010-05-29 11:12:08 ---
Closing invalid.