crash on quick exit after program start

[Ai_Tak]

I opened warzone and then changed my mind and quit, the program crashed prompted to send a Winqual error report to microsoft. It also triggered my configured aedebugger and I got a crashdump. I don't have the debugging symbols (where can I get them?) loaded for warzone, but from what I can see it was trying to run code from an unloaded module.

Here's what it has for a stack trace:

<Unloaded_wrap_oal.dll>+0x2f6c0
OpenAL32!alcGetError+0x60
warzone2100+0x116c3f
warzone2100+0x117d65
warzone2100+0x1154ba
warzone2100+0x67a5a
msvcrt!_cinit+0x9a
msvcrt!exit+0x12
warzone2100+0x198356
warzone2100+0x198404
warzone2100+0x197db9
warzone2100+0x10a7
warzone2100+0x1123
kernel32!BaseProcessStart+0x23

[Ai_Tak]

I thought it would at least format some simple text right, here it is again:

<Unloaded_wrap_oal.dll>+0x2f6c0
OpenAL32!alcGetError+0x60
warzone2100+0x116c3f
warzone2100+0x117d65
warzone2100+0x1154ba
warzone2100+0x67a5a
msvcrt!_cinit+0x9a
msvcrt!exit+0x12
warzone2100+0x198356
warzone2100+0x198404
warzone2100+0x197db9
warzone2100+0x10a7
warzone2100+0x1123
kernel32!BaseProcessStart+0x23

[Zarel]

Trac doesn't support automatic linebreaks for some reason. :/

Can you do an extended stack trace? That stack trace has no information at all. At least send the stack trace from the default crash handler in warzone2100.RPT

[Ai_Tak]

It didn't generate a warzone2100.RPT file, it was an unhandled exception, windows invoked the configured aedebugger(drwatson) to catch memory dump of the crashing process. The stack trace lacks function names because I don't have any debugging symbols for warzone.exe. The most details I can give you (without debugging symbols) is the output from !analyze -v (including stack trace):

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************

FAULTING_IP: 
wrap_oal+2f6c0
0346f6c0 ??              ???

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0346f6c0 (<Unloaded_wrap_oal.dll>+0x0002f6c0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0346f6c0
Attempt to read from address 0346f6c0

DEFAULT_BUCKET_ID:  BAD_INSTRUCTION_PTR

PROCESS_NAME:  warzone2100.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  0346f6c0

READ_ADDRESS:  0346f6c0 

FOLLOWUP_IP: 
wrap_oal+2f6c0
0346f6c0 ??              ???

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

IP_MODULE_UNLOADED: 
wrap_oal+2f6c0
0346f6c0 ??              ???

FAULTING_THREAD:  00000b54

PRIMARY_PROBLEM_CLASS:  BAD_INSTRUCTION_PTR

BUGCHECK_STR:  APPLICATION_FAULT_BAD_INSTRUCTION_PTR

LAST_CONTROL_TRANSFER:  from 10003e60 to 0346f6c0

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
0022fdac 10003e60 09330020 00000000 00518408 <Unloaded_wrap_oal.dll>+0x2f6c0
0022fde8 00516c3f 026b42b0 007f3924 77c2c2e3 OpenAL32!alcGetError+0x60
0022fe08 00517d65 00000001 00000000 0022fe38 warzone2100+0x116c3f
0022fe18 005154ba 0383b7f8 77c35c94 77c3a52e warzone2100+0x117d65
0022fe38 00467a5a 77c34e29 026d5708 77c3a5eb warzone2100+0x1154ba
0022fe58 77c39e24 0000000c 0022fe78 77c39e90 warzone2100+0x67a5a
0022fe64 77c39e90 00000000 00000000 026d27a4 msvcrt!_cinit+0x9a
0022fe78 00598356 00000000 026d5708 0000000c msvcrt!exit+0x12
0022fea8 00598404 00000001 026d5708 00000036 warzone2100+0x198356
0022fed8 00597db9 00400000 00000000 002423c5 warzone2100+0x198404
0022ff58 004010a7 00597c80 00401066 0022ff78 warzone2100+0x197db9
0022ffa0 00401123 00000002 8058306f 7c90dcba warzone2100+0x10a7
0022ffc0 7c817077 00390033 002d0038 7ffde000 warzone2100+0x1123
0022fff0 00000000 00401110 00000000 78746341 kernel32!BaseProcessStart+0x23


STACK_COMMAND:  ~0s; .ecxr ; kb

FAILED_INSTRUCTION_ADDRESS: 
wrap_oal+2f6c0
0346f6c0 ??              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  wrap_oal+2f6c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: wrap_oal

IMAGE_NAME:  wrap_oal.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  46927487

FAILURE_BUCKET_ID:  BAD_INSTRUCTION_PTR_c0000005_wrap_oal.dll!Unloaded

BUCKET_ID:  APPLICATION_FAULT_BAD_INSTRUCTION_PTR_BAD_IP_wrap_oal+2f6c0

[Safety0ff]

What are the versions of your wrap_oal.dll and OpenAL32.dll ?

Have you tried upgrading to the latest version?

Possible work around to follow... but I really don't see how this is happening.

[Safety0ff]

Possible workaround

[Ai_Tak]

OpenAL32.dll: 6.14.357.22

wrap_oal.dll: 2.1.8.1

Installed by oalinst.exe (2.0.3.0) that comes with both 2.2.4 and 2.3.0(beta)

Does anyone have debugging symbols for warzone.exe? Or could include full (built-in) debugging symbols with the next beta?

[Safety0ff]

I'm curious as to what would happen if you installed the latest version: ​http://connect.creativelabs.com/openal/Downloads/Forms/AllItems.aspx

(Try at your own peril.)

[Safety0ff]

Reference note: #1451 was a duplicate (contains useful information.)

[Zarel]

(In [9527]) 2.3: Fix bug #1444 - crash upon exit - patch provided by Safety0ff.

[Zarel]

(In [9528]) Fix bug #1444 - crash upon exit - patch provided by Safety0ff.