[Bug 14970] New: everquest causes a crash of wine in ntdll

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

Summary: everquest  causes a crash of wine in ntdll
           Product: Wine
           Version: 1.1.3
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ntdll
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
                CC: [e-mail]

When everquest starts up and begins to load into the game
wine crashes in a critical block in ntdll leaving the ll driver open:

err:ntdll:RtlpWaitForCriticalSection section 0x60b2f1c0 "x11drv_main.c:
X11DRV_CritSection" wait timed out in thread 0040, blocked by 002d, retrying
(60 sec)
fixme:winmm:MMDRV_Exit Closing while ll-driver open
fixme:winmm:MMDRV_Exit Closing while ll-driver open

[Bug 14970] everquest causes a crash of wine in ntdll

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

Vitaliy Margolen  changed:

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

--- Comment #1 from Vitaliy Margolen   2008-08-23 20:16:19 ---
This is not a crash.

[Bug 14970] everquest causes a crash of wine in ntdll

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

--- Comment #2 from chris ahrendt   2008-08-23 20:21:50 ---
The above was the output with no traces turned on...  
so it does crash...

[Bug 14970] everquest causes a crash of wine in ntdll

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

chris ahrendt  changed:

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

--- Comment #3 from chris ahrendt   2008-08-23 20:22:39 ---
The above was the output with no traces turned on...  
so it does crash...

[Bug 14970] everquest causes a crash of wine in ntdll

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

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|ntdll                       |-unknown

--- Comment #4 from Vitaliy Margolen   2008-08-23 21:19:04 ---
Then keep adding more information. "program crashes" is not enough.

[Bug 14970] everquest causes a crash of wine in ntdll

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

--- Comment #5 from Vitaliy Margolen   2008-08-23 21:20:22 ---
For one attach complete terminal out as-is. Then +relay. Then at least mention
what hardware you have? What video drivers? Have you removed ~/.wine directory
and reinstalled the program?

[Bug 14970] everquest causes a crash of wine in ntdll

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

--- Comment #6 from chris ahrendt   2008-08-23 22:17:04 ---
RHEL 5.2

ATI Firegl

Attached you will find both the relay output and the d3d , ntdll and the MMDRV
driver output as well in the 2 attachments.

I have deleted the .wine directory and installed it from scratch...

Did an empty .wine directory as well as one with dx9c installed as well...

all do the same

hardware :

T60P 4 gigs of memory 
ATI Firegl 5200 with 256 vido memory
1 tb of storage

[Bug 14970] everquest causes a crash of wine in ntdll

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

--- Comment #7 from chris ahrendt   2008-08-23 22:23:07 ---
Created an attachment (id=15582)
 --> (http://bugs.winehq.org/attachment.cgi?id=15582)
this is the d3d , ntdll and MMDRV output

[Bug 14970] everquest crashes

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

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|everquest  causes a crash of|everquest crashes
                   |wine in ntdll               |

--- Comment #8 from Vitaliy Margolen   2008-08-23 22:51:34 ---
Add +seh,+tid if talking about crash (to other channels). Also how is this
different then generic bug with ATI drivers?

You just created 3 separate bugs and in all the problem - everquest crashes.
How the hell can you see 3!!! separate causes of the same problem?!

Unless you clearly state why they all different, they will be marked as a
duplicates of each other.

[Bug 14970] everquest crashes

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

--- Comment #9 from chris ahrendt   2008-08-23 22:59:41 ---
Because it has nothing to do with ATI.. its the multi media driver that its
having an issue with.

Also it is in ntdll that the lock occurs.. both of which have nothing to do
with the ATI issues.

[Bug 14970] everquest crashes

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

--- Comment #10 from Vitaliy Margolen   2008-08-24 00:53:03 ---
(In reply to comment #9)
> its the multi media driver that its having an issue with.

And you know that how?
> Also it is in ntdll that the lock occurs..

Of course it is, that's where all the CriticalSection functions are. Except
that doesn't mean there is something wrong there...

[Bug 14970] everquest crashes

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

--- Comment #11 from chris ahrendt   2008-08-25 16:19:42 ---
here is the seh exception with the tid  trace....

I opened 3 different bugs in the bug database because they are three seperate
issues which are not related to one another...

In the SED and TID you will find the exception being raised

[Bug 14970] everquest crashes

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

--- Comment #12 from chris ahrendt   2008-08-25 16:31:58 ---
Created an attachment (id=15640)
 --> (http://bugs.winehq.org/attachment.cgi?id=15640)
this is the sed and tid with the exception output

[Bug 14970] everquest crashes

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

--- Comment #13 from chris ahrendt   2008-08-25 16:37:24 ---
Created an attachment (id=15641)
 --> (http://bugs.winehq.org/attachment.cgi?id=15641)
here is another stack dump as well

[Bug 14970] everquest crashes

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

Vitaliy Margolen  changed:

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

--- Comment #14 from Vitaliy Margolen   2008-08-25 16:47:25 ---
What the hell is that stuff you attached???
d3d10??!! What are you trying to do there with DX10??

You mixing again 100 different things here!

Closing invalid. You can't pile all your crashes into one bug and hope they
magically fix themselves!

[Bug 14970] everquest crashes

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

Vitaliy Margolen  changed:

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

--- Comment #15 from Vitaliy Margolen   2008-08-25 16:48:22 ---
Totally bogus crashes:
d3d10
broken ati drivers
wined3d crash related to broken ati drivers and missconfigured system.

[Bug 14970] everquest crashes

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

chris ahrendt  changed:

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

--- Comment #16 from chris ahrendt   2008-08-25 17:56:15 ---
I am doing nothing with D3d10
and the things attached are what you asked for in the bug..
they are the Sed output and the TID output... d3d10 is disabled in the wine
configuration.

[Bug 14970] everquest crashes

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

Vitaliy Margolen  changed:

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

--- Comment #17 from Vitaliy Margolen   2008-08-25 18:08:28 ---
(In reply to comment #16)
> I am doing nothing with D3d10
> and the things attached are what you asked for in the bug..
> they are the Sed output and the TID output... d3d10 is disabled in the wine
> configuration.

Then what are those errors in the second attachment?

DO NOT REOPEN! You showed time and time again that your bugs nothing more then
piled problems from all over the place. And that you chasing ghosts. You
problem is junk ati drivers - go fix that fist.

[Bug 14970] everquest crashes

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

Vitaliy Margolen  changed:

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

--- Comment #18 from Vitaliy Margolen   2008-08-25 18:09:01 ---
Closing invalid. DO NOT REOPEN until you get really working drivers.

[Bug 14970] everquest crashes

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

chris ahrendt  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #15582|0                           |1
        is obsolete|                            |
  Attachment #15640|0                           |1
        is obsolete|                            |
  Attachment #15641|0                           |1
        is obsolete|                            |

--- Comment #19 from chris ahrendt   2008-08-25 18:44:43 ---
Created an attachment (id=15643)
 --> (http://bugs.winehq.org/attachment.cgi?id=15643)
here is a log with nothing pointing to d3d10 nor the ATI drivers

I do not see anywhere in here where this points to a ATI driver issue and
believe your anti-ATI bias from the development list has bled over to this.

There is nothing  in this log to point to an ATI failure.

the winmm is not the ATI
I do not see the usual ATI issues within this log. 
The Check Texture error earlier in the log is not this problem and had another
bug opened and then closed as a dupe against the Age of conan issues.

If you look there is a section at the end

0022:fixme:dbghelp:dump_system_info fill in CPU vendorID and feature set
0022:err:d3d:IWineD3DDeviceImpl_Reset Cannot change the back buffer format yet
0022:err:d3d:IWineD3DDeviceImpl_Reset What do do about a changed auto depth
stencil parameter?
0034:err:ntdll:RtlpWaitForCriticalSection section 0x60b921c0 "x11drv_main.c:
X11DRV_CritSection" wait timed out in thread 0034, blocked by 0022, retrying
(60 sec)
0022:fixme:winmm:MMDRV_Exit Closing while ll-driver open
0022:fixme:winmm:MMDRV_Exit Closing while ll-driver open

the winmm error is not caused by ATI... it should not close while leaving the
driver open.

the critical section could be caused by the ATI or could be caused by another
multi-media device... it just depends on where it is in the call..

keep the Bias out of the bug list

[Bug 14970] everquest crashes

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

chris ahrendt  changed:

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

--- Comment #20 from chris ahrendt   2008-08-25 18:49:43 ---
0022:err:d3d:IWineD3DDeviceImpl_Reset Cannot change the back buffer format yet
0022:err:d3d:IWineD3DDeviceImpl_Reset What do do about a changed auto depth

If you look also these calls above also happen on my machine with the nvidia
drivers.  So no ATI issue on that machine.. the mm bug leaving the ll driver
open happens there as well.. again no ATI.

Again please keep the ATI bias you have shown on the dev list out of these

thanks

[Bug 14970] everquest crashes

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

--- Comment #21 from Vitaliy Margolen   2008-08-25 22:01:29 ---
> 0022:fixme:dbghelp:dump_system_info fill in CPU vendorID and feature set

^^^^^ this is the point it crashed and collecting information for the memory
dump.
> 0022:err:d3d:IWineD3DDeviceImpl_Reset Cannot change the back buffer format yet
> 0022:err:d3d:IWineD3DDeviceImpl_Reset What do do about a changed auto depth

Please find where that memory dump and run winedbg against it.

If you can't, then attach +relay,+d3d,+seh,+tid

[Bug 14970] everquest crashes

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

--- Comment #22 from chris ahrendt   2008-08-26 13:58:34 ---
Created an attachment (id=15668)
 --> (http://bugs.winehq.org/attachment.cgi?id=15668)
exception sed _d3d and tid....

[Bug 14970] everquest crashes

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

--- Comment #23 from Vitaliy Margolen   2008-08-26 15:15:13 ---
(In reply to comment #22)
> Created an attachment (id=15668)

--> (http://bugs.winehq.org/attachment.cgi?id=15668) [details]
> exception sed _d3d and tid....

WTF is that? Read what I asked you.

[Bug 14970] everquest crashes

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

--- Comment #24 from chris ahrendt   2008-08-26 23:13:41 ---
(In reply to comment #23)
> (In reply to comment #22)
> > Created an attachment (id=15668)

--> (http://bugs.winehq.org/attachment.cgi?id=15668) [details] [details]
> > exception sed _d3d and tid....
>
> WTF is that? Read what I asked you.

That is the crash you asked for... the relay dump is 1. too big to put here and
2. when I can get it to run causes wine to get into a loop where the
application will not start because it times out.
3. The only way to get the dump is to put +sed,+d3d,+tid,-debuginfo  in the
export and then run the application.

[Bug 14970] everquest crashes in winemm

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

chris ahrendt  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|everquest crashes           |everquest crashes in winemm

[Bug 14970] everquest crashes in winemm

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

--- Comment #25 from Vitaliy Margolen   2008-08-27 00:54:15 ---
I have not asked for "sed" it's "seh".

Other then that, you posted some other crash yet again. Now it's what 4
different crash in one single bug? Oh and btw this crash is a duplicate of
several other bugs.

[Bug 14970] everquest crashes

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

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID
            Summary|everquest crashes in winemm |everquest crashes

--- Comment #26 from Vitaliy Margolen   2008-08-27 00:55:31 ---
Closing. Since you keep insisting this is winmm crash. Yet all your crashes
indicating this is same exact problem - bad ati drivers.

[Bug 14970] everquest crashes

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

Vitaliy Margolen  changed:

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

--- Comment #27 from Vitaliy Margolen   2008-08-27 00:55:39 ---
Closing

[Bug 14970] everquest crashes

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

chris ahrendt  changed:

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

--- Comment #28 from chris ahrendt   2008-08-27 08:13:41 ---
This is the same crash I have been talking about all along..

It is not an ATI bug...

Reopening

[Bug 14970] everquest crashes

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

--- Comment #29 from chris ahrendt   2008-08-27 08:17:14 ---
Again just because you have a bias and a vendetta against ATI don't take it out
here... it is a bug. Wine should not have an exception. Period.

[Bug 14970] everquest crashes

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

--- Comment #30 from chris ahrendt   2008-08-27 08:39:41 ---
Created an attachment (id=15681)
 --> (http://bugs.winehq.org/attachment.cgi?id=15681)
here is the same error as the previous attachment..

Here is the same error I am talking about in winmm
with  export WINEDEBUG=+d3d,+seh,+tid,+driver,+winmm

AGAIN there is nothing in this trace that points to a ATI driver bug for the
particular problem I am reporting here:

as a matter of fact if you look:

the ipixel format is found... a new context is found... textures are created...

then on thread 0x38  is when winmm begins having problems!

+relay will not work in this case due to a timing issue with the application.
Because +relay takes too much time out of the application timeslice it never
logs into the program nor does it get the crash I am reporting because of this.

Again I am not reporting an ATI issue..  this is the same bug and same issue I
have been reporting since the start. This is not a 4th or 5th issue but all the
same issue that is happening in winmm.

[Bug 14970] everquest crashes

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

--- Comment #31 from chris ahrendt   2008-08-27 08:43:33 ---
By the way also if you look at the trace where the X11DRV_CritSection  wait
time out occurs in thread 1c you will see that it is blocked on thread 38!

if you look below the error: Wow.. thread 38 is winmm:MMDRV!!!!!!!!

again.. where is ATI??? this is NOT AN ATI BUG as much as you want it to be.

[Bug 14970] everquest crashes

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

--- Comment #32 from chris ahrendt   2008-08-27 09:36:26 ---
additionally if it was an ATI driver issue then ulimit -s unlimited would cause
the mmdrv issue to go away.. which it does not..

[Bug 14970] everquest crashes

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

--- Comment #33 from chris ahrendt   2008-08-29 16:29:10 ---
once the crash occurs the sound device is locked and no sound (either within
wine or outside of wine such as a media player) is able to play.

[Bug 14970] everquest crashes

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

chris ahrendt  changed:

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

[Bug 14970] everquest crashes

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

Dmitry Timoshkov  changed:

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

--- Comment #34 from Dmitry Timoshkov   2008-09-02 22:23:09 ---
http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity

[Bug 14970] everquest crashes

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

--- Comment #35 from chris ahrendt   2008-09-03 19:22:35 ---
Latest git finally returns this error:

err:dsound:DSOUND_MixOne Fatal error. Under/Overflow? primary_done=40960,
mixpos=44800/69120 (44800/69120), primary_mixpos=2560, writepos=5760,
mixlen=4480
err:dsound:DSOUND_MixOne Fatal error. Under/Overflow? primary_done=40960,
mixpos=44800/69120 (44800/69120), primary_mixpos=2560, writepos=5760,
mixlen=4480
err:dsound:DSOUND_MixOne Fatal error. Under/Overflow? primary_done=40960,
mixpos=44800/69120 (44800/69120), primary_mixpos=2560, writepos=5760,
mixlen=4480
fixme:winmm:MMDRV_Exit Closing while ll-driver open
fixme:winmm:MMDRV_Exit Closing while ll-driver open

[Bug 14970] everquest crashes in winemm

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

chris ahrendt  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|everquest crashes           |everquest crashes in winemm

[Bug 14970] everquest crashes in winmm

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

chris ahrendt  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|everquest crashes in winemm |everquest crashes in winmm

[Bug 14970] everquest crashes in winmm

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

--- Comment #36 from Jeff Zaroyko   2008-09-10 16:31:47 ---
chris

what happens if you disable sound in winecfg?

[Bug 14970] everquest crashes in winmm

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

--- Comment #37 from chris ahrendt   2008-09-10 17:24:24 ---
The MMDRV error does not occur....

It loads up... gets into the game.... and then I move around and it crashes..

So disabling the sound prevents the MMDRV error and now there is a collision
bug =)... so the work around is to disable sound in the application.

Chris

[Bug 14970] everquest crashes in winmm

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

--- Comment #38 from Jeff Zaroyko   2008-09-10 18:50:33 ---
(In reply to comment #37)
> The MMDRV error does not occur....
>
> It loads up... gets into the game.... and then I move around and it crashes..
>
> So disabling the sound prevents the MMDRV error and now there is a collision
> bug =)... so the work around is to disable sound in the application.
>
> Chris

can you post a backtrace of the crash you experience with the sound enabled? 
try running everquest from winedbg to catch the exception in the debugger.

[Bug 14970] everquest crashes in winmm

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

--- Comment #39 from Austin English   2009-03-10 15:03:23 ---
Is this still an issue in current (1.1.16 or newer) wine?

[Bug 14970] everquest crashes in winmm

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

--- Comment #40 from chris ahrendt   2009-03-11 15:46:05 ---
will have to check

[Bug 14970] everquest crashes in winmm

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

--- Comment #41 from chris ahrendt   2009-04-18 20:21:26 ---
Its random and a bit more stable. but occurs randomly in the newer zones

[Bug 14970] everquest crashes in winmm

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

--- Comment #42 from Jeff Zaroyko   2009-04-18 20:49:14 ---
still waiting 6 months for you to post a backtrace

[Bug 14970] everquest crashes in winmm

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

--- Comment #43 from chris ahrendt   2009-04-18 21:47:14 ---
ok will try that tonight

Chris

[Bug 14970] everquest crashes in winmm

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

chris ahrendt  changed:

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

--- Comment #44 from chris ahrendt   2009-04-18 22:10:13 ---
Cant get to consistantly reproduce so closing until I can

[Bug 14970] everquest crashes in winmm

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

chris ahrendt  changed:

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

--- Comment #45 from chris ahrendt   2009-04-18 22:16:25 ---
Don't know if this helps but I just got it to do this
with regular wine :

E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
EOZy5MvjXwqAsi: pulse.c:200: pulse_new: Assertion `p->context' failed.
err:module:attach_process_dlls "winmm.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for
L"F:\everquest\eqgame.exe" failed, status 80000101
fixme:shdocvw:OleInPlaceObject_UIDeactivate (0x158748)
fixme:shdocvw:OleInPlaceObject_InPlaceDeactivate (0x158748)
fixme:shdocvw:OleObject_Close (0x158748)->(1)
fixme:shdocvw:OleInPlaceObject_UIDeactivate (0x158748)
fixme:shdocvw:OleInPlaceObject_InPlaceDeactivate (0x158748)
fixme:shdocvw:OleObject_Close (0x158748)->(1)
fixme:shdocvw:ViewObject_SetAdvise (0x158748)->(1 00000000 (nil))
fixme:shdocvw:OleInPlaceObject_UIDeactivate (0xad3d450)
fixme:shdocvw:OleInPlaceObject_InPlaceDeactivate (0xad3d450)
fixme:shdocvw:OleObject_Close (0xad3d450)->(1)
fixme:shdocvw:OleInPlaceObject_UIDeactivate (0xad3d450)
fixme:shdocvw:OleInPlaceObject_InPlaceDeactivate (0xad3d450)
fixme:shdocvw:OleObject_Close (0xad3d450)->(1)
fixme:shdocvw:ViewObject_SetAdvise (0xad3d450)->(1 00000000 (nil))

but am having a hard time getting a backtrace in winedbg... it seems to shift
the stack and gets farther...

[Bug 14970] everquest crashes in winmm

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

--- Comment #46 from Vitaliy Margolen   2009-04-19 12:25:24 ---
> EOZy5MvjXwqAsi: pulse.c:200: pulse_new: Assertion `p->context' failed.

You using pulseaudio - it conflicts with Wine. Remove it / kill it / disable it
and try again.

[Bug 14970] everquest crashes in winmm

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

chris ahrendt  changed:

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

--- Comment #47 from chris ahrendt   2009-04-19 17:33:44 ---
Fixed with latest GIT and removal of pulse audio

[Bug 14970] everquest crashes in winmm

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

Alexandre Julliard  changed:

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

--- Comment #48 from Alexandre Julliard   2009-04-24 12:15:41 ---
Closing bugs fixed in 1.1.20.