Audio application crashes with madExcept enabled

delphi package - automated exception handling

Audio application crashes with madExcept enabled

Postby yps77 » Wed Feb 22, 2017 9:50 am

Hi,

I'm a user of the commercial edition of madExcept (using v4.0.16 currently), and I'm developing an audio application in Delphi XE6.

One of my users complained that the application would crash when he attaches a particular USB audio interface (RME Babyface) to his computer. It's the kind of "Program has stopped working" error, so madExcept is not handling that exception.

I am pretty sure that the audio driver is messing something up; but after a bit of debugging, it turned out that the crash only happens when madExcept is enabled. As soon as I remove madExept from the project, or use PauseMadExcept(true) at the beginning of my code, everything works just fine. Also tried to turn on buffer overrun detection in madExept, doesn't make any difference.

We were able to catch a mini dump file from Windows, and decoding it in WinDbg, it seems that the cause of the crash is an Access Violation in FmtStr, called from some madExcept exception handler. I'm attaching the log below. Any idea why this would happen?


Thanks for your help,

Torben

Code: Select all

Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\temp\myapplication.exe.10540.dmp]
WARNING: Minidump contains unknown stream type 0x15
WARNING: Minidump contains unknown stream type 0x16
User Mini Dump File: Only registers, stack and portions of memory are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\projects\myapplication\source
Symbol search path is: C:\projects\myapplication\source
Executable search path is:
Windows 8 Version 14393 MP (8 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
Built by: 10.0.14393.206 (rs1_release.160915-0644)
Machine Name:
Debug session time: Tue Feb 21 22:43:00.000 2017 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:00:05.000
................................................................
..............................
Loading unloaded module list
...
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(292c.283c): Access violation - code c0000005 (first/second chance not available)
*** WARNING: Unable to verify timestamp for ntdll.dll
*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
eax=00000002 ebx=0384085c ecx=000a1e70 edx=0384085c esi=000a1e70 edi=00000003
eip=004537ff esp=000a0dc0 ebp=000a1dc0 iopl=0         nv up ei pl nz ac pe cy
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00210217
myapplication!System.SysUtils.FmtStr+0xf:
004537ff 50              push    eax
0:000> .load wow64exts
0:000> .effmach x86
Effective machine: x86 compatible (x86)
0:000> .ecxr
eax=00000002 ebx=0384085c ecx=000a1e70 edx=0384085c esi=000a1e70 edi=00000003
eip=004537ff esp=000a0dc0 ebp=000a1dc0 iopl=0         nv up ei pl nz ac pe cy
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00210217
myapplication!System.SysUtils.FmtStr+0xf:
004537ff 50              push    eax
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

***** OS symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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: ntdll!_PEB                                    ***
***                                                                   ***
*************************************************************************
Unable to load image C:\Windows\System32\kernel32.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kernel32.dll
*** ERROR: Module load completed but symbols could not be loaded for kernel32.dll

************* Symbol Loading Error Summary **************
Module name            Error
kernel32               PDB not found : c:\projects\myapplication\source\symbols\dll\wkernel32.pdb

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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: nt!IMAGE_NT_HEADERS32                         ***
***                                                                   ***
*************************************************************************
Unable to load image C:\Windows\System32\ole32.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ole32.dll
*** ERROR: Module load completed but symbols could not be loaded for ole32.dll

************* Symbol Loading Error Summary **************
Module name            Error
ole32                  PDB not found : c:\projects\myapplication\source\symbols\dll\ole32.pdb

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
Unable to load image C:\Windows\System32\combase.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for combase.dll
*** ERROR: Module load completed but symbols could not be loaded for combase.dll

************* Symbol Loading Error Summary **************
Module name            Error
combase                PDB not found : c:\projects\myapplication\source\symbols\dll\combase.pdb

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
Unable to load image C:\Windows\System32\KERNELBASE.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for KERNELBASE.dll
*** ERROR: Module load completed but symbols could not be loaded for KERNELBASE.dll
*** WARNING: Unable to verify checksum for bass.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for bass.dll -
*** The OS name list needs to be updated! Unknown Windows version: 10.0 ***

FAULTING_IP:
myapplication!System.SysUtils.FmtStr+f
004537ff 50              push    eax

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 004537ff (myapplication!System.SysUtils.FmtStr+0x0000000f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 000a0dbc
Attempt to write to address 000a0dbc

CONTEXT:  00000000 -- (.cxr 0x0;r)
eax=00000002 ebx=0384085c ecx=000a1e70 edx=0384085c esi=000a1e70 edi=00000003
eip=004537ff esp=000a0dc0 ebp=000a1dc0 iopl=0         nv up ei pl nz ac pe cy
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00210217
myapplication!System.SysUtils.FmtStr+0xf:
004537ff 50              push    eax

PROCESS_NAME:  myapplication.exe

ADDITIONAL_DEBUG_TEXT: 
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: 77ba0000 ntdll

DEBUG_FLR_IMAGE_TIMESTAMP:  58ac9dd5

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  000a0dbc

WRITE_ADDRESS:  000a0dbc

FOLLOWUP_IP:
myapplication!System.SysUtils.FmtStr+f
004537ff 50              push    eax

APP:  myapplication.exe

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS

BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS_INVALID_STACK_ACCESS

LAST_CONTROL_TRANSFER:  from 004537d3 to 004537ff

STACK_TEXT: 
000a1dc0 004537d3 013fde9c 00000003 000a1dec myapplication!System.SysUtils.FmtStr+0xf
000a1dd0 004537b8 000a1e20 013fde9c 0a59cf90 myapplication!System.SysUtils.Format+0x13
000a1dec 00458bb9 000a1e20 000a1e04 00458bda myapplication!System.SysUtils.Format+0x20
000a1e24 00459239 00000003 000a1e70 000a20c8 myapplication!System.SysUtils.Exception.CreateFmt+0x39
000a20bc 0045934a 000a20e8 000a2114 004593b5 myapplication!System.SysUtils.CreateAVObject+0x171
000a20e8 004a8112 00000000 00000000 00000000 myapplication!System.SysUtils.GetExceptionObject+0x6a
000a2120 77c22d44 000a2204 000a2734 000a2254 myapplication!madExcept.MyExceptObjProc+0x3a
WARNING: Stack unwind information not available. Following frames may be wrong.
000a21ec 77c108ef 000a2204 000a2254 000a2204 ntdll+0x82d44
000a2784 0047056e 5fb50000 00000000 000a27a8 ntdll+0x708ef
000a27a8 004705e4 00000000 00000000 000a27d8 myapplication!madExcept.IsValidObjectEx+0x7a
000a27d0 004a7efa 000a282c 004a8092 000a27fc myapplication!madExcept.IsValidObject+0x34
000a27fc 004a8139 000a2968 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a2838 77c22d44 000a2918 000a4e8c 000a2968 myapplication!madExcept.MyExceptObjProc+0x61
000a2900 77c108ef 000a2918 000a2968 000a2918 ntdll+0x82d44
000a4e48 004537d3 013fde9c 00000003 000a4e74 ntdll+0x708ef
000a4e58 004537b8 000a4ea8 013fde9c 0a59cf40 myapplication!System.SysUtils.Format+0x13
000a4e74 00458bb9 000a4ea8 000a4e8c 00458bda myapplication!System.SysUtils.Format+0x20
000a4eac 00459239 00000003 000a4ef8 000a5150 myapplication!System.SysUtils.Exception.CreateFmt+0x39
000a5144 0045934a 000a5170 000a519c 004593b5 myapplication!System.SysUtils.CreateAVObject+0x171
000a5170 004a8112 00000000 00000000 00000000 myapplication!System.SysUtils.GetExceptionObject+0x6a
000a51a8 77c22d44 000a528c 000a57bc 000a52dc myapplication!madExcept.MyExceptObjProc+0x3a
000a5274 77c108ef 000a528c 000a52dc 000a528c ntdll+0x82d44
000a580c 0047056e 5fb50000 00000000 000a5830 ntdll+0x708ef
000a5830 004705e4 00000000 00000000 000a5860 myapplication!madExcept.IsValidObjectEx+0x7a
000a5858 004a7efa 000a58b4 004a8092 000a5884 myapplication!madExcept.IsValidObject+0x34
000a5884 004a8139 000a59f4 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a58c0 77c22d44 000a59a4 000a5ed4 000a59f4 myapplication!madExcept.MyExceptObjProc+0x61
000a598c 77c108ef 000a59a4 000a59f4 000a59a4 ntdll+0x82d44
000a5f24 0047056e 5fb50000 00000000 000a5f48 ntdll+0x708ef
000a5f48 004705e4 00000000 00000000 000a5f78 myapplication!madExcept.IsValidObjectEx+0x7a
000a5f70 004a7efa 000a5fcc 004a8092 000a5f9c myapplication!madExcept.IsValidObject+0x34
000a5f9c 004a8139 000a610c 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a5fd8 77c22d44 000a60bc 000a65ec 000a610c myapplication!madExcept.MyExceptObjProc+0x61
000a60a4 77c108ef 000a60bc 000a610c 000a60bc ntdll+0x82d44
000a663c 0047056e 5fb50000 00000000 000a6660 ntdll+0x708ef
000a6660 004705e4 00000000 00000000 000a6690 myapplication!madExcept.IsValidObjectEx+0x7a
000a6688 004a7efa 000a66e4 004a8092 000a66b4 myapplication!madExcept.IsValidObject+0x34
000a66b4 004a8139 000a6824 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a66f0 77c22d44 000a67d4 000a6d04 000a6824 myapplication!madExcept.MyExceptObjProc+0x61
000a67bc 77c108ef 000a67d4 000a6824 000a67d4 ntdll+0x82d44
000a6d54 0047056e 5fb50000 00000000 000a6d78 ntdll+0x708ef
000a6d78 004705e4 00000000 00000000 000a6da8 myapplication!madExcept.IsValidObjectEx+0x7a
000a6da0 004a7efa 000a6dfc 004a8092 000a6dcc myapplication!madExcept.IsValidObject+0x34
000a6dcc 004a8139 000a6f3c 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a6e08 77c22d44 000a6eec 000a741c 000a6f3c myapplication!madExcept.MyExceptObjProc+0x61
000a6ed4 77c108ef 000a6eec 000a6f3c 000a6eec ntdll+0x82d44
000a746c 0047056e 5fb50000 00000000 000a7490 ntdll+0x708ef
000a7490 004705e4 00000000 00000000 000a74c0 myapplication!madExcept.IsValidObjectEx+0x7a
000a74b8 004a7efa 000a7514 004a8092 000a74e4 myapplication!madExcept.IsValidObject+0x34
000a74e4 004a8139 000a7654 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a7520 77c22d44 000a7604 000a7b34 000a7654 myapplication!madExcept.MyExceptObjProc+0x61
000a75ec 77c108ef 000a7604 000a7654 000a7604 ntdll+0x82d44
000a7b84 0047056e 5fb50000 00000000 000a7ba8 ntdll+0x708ef
000a7ba8 004705e4 00000000 00000000 000a7bd8 myapplication!madExcept.IsValidObjectEx+0x7a
000a7bd0 004a7efa 000a7c2c 004a8092 000a7bfc myapplication!madExcept.IsValidObject+0x34
000a7bfc 004a8139 000a7d6c 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a7c38 77c22d44 000a7d1c 000a824c 000a7d6c myapplication!madExcept.MyExceptObjProc+0x61
000a7d04 77c108ef 000a7d1c 000a7d6c 000a7d1c ntdll+0x82d44
000a829c 0047056e 5fb50000 00000000 000a82c0 ntdll+0x708ef
000a82c0 004705e4 00000000 00000000 000a82f0 myapplication!madExcept.IsValidObjectEx+0x7a
000a82e8 004a7efa 000a8344 004a8092 000a8314 myapplication!madExcept.IsValidObject+0x34
000a8314 004a8139 000a8484 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a8350 77c22d44 000a8434 000a8964 000a8484 myapplication!madExcept.MyExceptObjProc+0x61
000a841c 77c108ef 000a8434 000a8484 000a8434 ntdll+0x82d44
000a89b4 0047056e 5fb50000 00000000 000a89d8 ntdll+0x708ef
000a89d8 004705e4 00000000 00000000 000a8a08 myapplication!madExcept.IsValidObjectEx+0x7a
000a8a00 004a7efa 000a8a5c 004a8092 000a8a2c myapplication!madExcept.IsValidObject+0x34
000a8a2c 004a8139 000a8b9c 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a8a68 77c22d44 000a8b4c 000a907c 000a8b9c myapplication!madExcept.MyExceptObjProc+0x61
000a8b34 77c108ef 000a8b4c 000a8b9c 000a8b4c ntdll+0x82d44
000a90cc 0047056e 5fb50000 00000000 000a90f0 ntdll+0x708ef
000a90f0 004705e4 00000000 00000000 000a9120 myapplication!madExcept.IsValidObjectEx+0x7a
000a9118 004a7efa 000a9174 004a8092 000a9144 myapplication!madExcept.IsValidObject+0x34
000a9144 004a8139 000a92b4 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a9180 77c22d44 000a9264 000a9794 000a92b4 myapplication!madExcept.MyExceptObjProc+0x61
000a924c 77c108ef 000a9264 000a92b4 000a9264 ntdll+0x82d44
000a97e4 0047056e 5fb50000 00000000 000a9808 ntdll+0x708ef
000a9808 004705e4 00000000 00000000 000a9838 myapplication!madExcept.IsValidObjectEx+0x7a
000a9830 004a7efa 000a988c 004a8092 000a985c myapplication!madExcept.IsValidObject+0x34
000a985c 004a8139 000a99cc 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a9898 77c22d44 000a997c 000a9eac 000a99cc myapplication!madExcept.MyExceptObjProc+0x61
000a9964 77c108ef 000a997c 000a99cc 000a997c ntdll+0x82d44
000a9efc 0047056e 5fb50000 00000000 000a9f20 ntdll+0x708ef
000a9f20 004705e4 00000000 00000000 000a9f50 myapplication!madExcept.IsValidObjectEx+0x7a
000a9f48 004a7efa 000a9fa4 004a8092 000a9f74 myapplication!madExcept.IsValidObject+0x34
000a9f74 004a8139 000aa0e4 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000a9fb0 77c22d44 000aa094 000aa5c4 000aa0e4 myapplication!madExcept.MyExceptObjProc+0x61
000aa07c 77c108ef 000aa094 000aa0e4 000aa094 ntdll+0x82d44
000aa614 0047056e 5fb50000 00000000 000aa638 ntdll+0x708ef
000aa638 004705e4 00000000 00000000 000aa668 myapplication!madExcept.IsValidObjectEx+0x7a
000aa660 004a7efa 000aa6bc 004a8092 000aa68c myapplication!madExcept.IsValidObject+0x34
000aa68c 004a8139 000aa7fc 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000aa6c8 77c22d44 000aa7ac 000aacdc 000aa7fc myapplication!madExcept.MyExceptObjProc+0x61
000aa794 77c108ef 000aa7ac 000aa7fc 000aa7ac ntdll+0x82d44
000aad2c 0047056e 5fb50000 00000000 000aad50 ntdll+0x708ef
000aad50 004705e4 00000000 00000000 000aad80 myapplication!madExcept.IsValidObjectEx+0x7a
000aad78 004a7efa 000aadd4 004a8092 000aada4 myapplication!madExcept.IsValidObject+0x34
000aada4 004a8139 000aaf14 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000aade0 77c22d44 000aaec4 000ab3f4 000aaf14 myapplication!madExcept.MyExceptObjProc+0x61
000aaeac 77c108ef 000aaec4 000aaf14 000aaec4 ntdll+0x82d44
000ab444 0047056e 5fb50000 00000000 000ab468 ntdll+0x708ef
000ab468 004705e4 00000000 00000000 000ab498 myapplication!madExcept.IsValidObjectEx+0x7a
000ab490 004a7efa 000ab4ec 004a8092 000ab4bc myapplication!madExcept.IsValidObject+0x34
000ab4bc 004a8139 000ab62c 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000ab4f8 77c22d44 000ab5dc 000abb0c 000ab62c myapplication!madExcept.MyExceptObjProc+0x61
000ab5c4 77c108ef 000ab5dc 000ab62c 000ab5dc ntdll+0x82d44
000abb5c 0047056e 5fb50000 00000000 000abb80 ntdll+0x708ef
000abb80 004705e4 00000000 00000000 000abbb0 myapplication!madExcept.IsValidObjectEx+0x7a
000abba8 004a7efa 000abc04 004a8092 000abbd4 myapplication!madExcept.IsValidObject+0x34
000abbd4 004a8139 000abd44 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000abc10 77c22d44 000abcf4 000ac224 000abd44 myapplication!madExcept.MyExceptObjProc+0x61
000abcdc 77c108ef 000abcf4 000abd44 000abcf4 ntdll+0x82d44
000ac274 0047056e 5fb50000 00000000 000ac298 ntdll+0x708ef
000ac298 004705e4 00000000 00000000 000ac2c8 myapplication!madExcept.IsValidObjectEx+0x7a
000ac2c0 004a7efa 000ac31c 004a8092 000ac2ec myapplication!madExcept.IsValidObject+0x34
000ac2ec 004a8139 000ac45c 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000ac328 77c22d44 000ac40c 000ac93c 000ac45c myapplication!madExcept.MyExceptObjProc+0x61
000ac3f4 77c108ef 000ac40c 000ac45c 000ac40c ntdll+0x82d44
000ac98c 0047056e 5fb50000 00000000 000ac9b0 ntdll+0x708ef
000ac9b0 004705e4 00000000 00000000 000ac9e0 myapplication!madExcept.IsValidObjectEx+0x7a
000ac9d8 004a7efa 000aca34 004a8092 000aca04 myapplication!madExcept.IsValidObject+0x34
000aca04 004a8139 000acb74 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000aca40 77c22d44 000acb24 000ad054 000acb74 myapplication!madExcept.MyExceptObjProc+0x61
000acb0c 77c108ef 000acb24 000acb74 000acb24 ntdll+0x82d44
000ad0a4 0047056e 5fb50000 00000000 000ad0c8 ntdll+0x708ef
000ad0c8 004705e4 00000000 00000000 000ad0f8 myapplication!madExcept.IsValidObjectEx+0x7a
000ad0f0 004a7efa 000ad14c 004a8092 000ad11c myapplication!madExcept.IsValidObject+0x34
000ad11c 004a8139 000ad28c 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000ad158 77c22d44 000ad23c 000ad76c 000ad28c myapplication!madExcept.MyExceptObjProc+0x61
000ad224 77c108ef 000ad23c 000ad28c 000ad23c ntdll+0x82d44
000ad7bc 0047056e 5fb50000 00000000 000ad7e0 ntdll+0x708ef
000ad7e0 004705e4 00000000 00000000 000ad810 myapplication!madExcept.IsValidObjectEx+0x7a
000ad808 004a7efa 000ad864 004a8092 000ad834 myapplication!madExcept.IsValidObject+0x34
000ad834 004a8139 000ad9a4 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000ad870 77c22d44 000ad954 000ade84 000ad9a4 myapplication!madExcept.MyExceptObjProc+0x61
000ad93c 77c108ef 000ad954 000ad9a4 000ad954 ntdll+0x82d44
000aded4 0047056e 5fb50000 00000000 000adef8 ntdll+0x708ef
000adef8 004705e4 00000000 00000000 000adf28 myapplication!madExcept.IsValidObjectEx+0x7a
000adf20 004a7efa 000adf7c 004a8092 000adf4c myapplication!madExcept.IsValidObject+0x34
000adf4c 004a8139 000ae0bc 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000adf88 77c22d44 000ae06c 000ae59c 000ae0bc myapplication!madExcept.MyExceptObjProc+0x61
000ae054 77c108ef 000ae06c 000ae0bc 000ae06c ntdll+0x82d44
000ae5ec 0047056e 5fb50000 00000000 000ae610 ntdll+0x708ef
000ae610 004705e4 00000000 00000000 000ae640 myapplication!madExcept.IsValidObjectEx+0x7a
000ae638 004a7efa 000ae694 004a8092 000ae664 myapplication!madExcept.IsValidObject+0x34
000ae664 004a8139 000ae7d4 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000ae6a0 77c22d44 000ae784 000aecb4 000ae7d4 myapplication!madExcept.MyExceptObjProc+0x61
000ae76c 77c108ef 000ae784 000ae7d4 000ae784 ntdll+0x82d44
000aed04 0047056e 5fb50000 00000000 000aed28 ntdll+0x708ef
000aed28 004705e4 00000000 00000000 000aed58 myapplication!madExcept.IsValidObjectEx+0x7a
000aed50 004a7efa 000aedac 004a8092 000aed7c myapplication!madExcept.IsValidObject+0x34
000aed7c 004a8139 000aeeec 00000000 00000000 myapplication!madExcept.SetLastException+0x66
000aedb8 77c22d44 000aee9c 000af3cc 000aeeec myapplication!madExcept.MyExceptObjProc+0x61
000aee84 77c108ef 000aee9c 000aeeec 000aee9c ntdll+0x82d44
000af41c 0047056e 5fb50000 00000000 000af440 ntdll+0x708ef
000af440 004705e4 00000000 00000000 000af470 myapplication!madExcept.IsValidObjectEx+0x7a
000af468 004a7efa 000af4c4 004a8092 000af494 myapplication!madExcept.IsValidObject+0x34
000af494 004a8139 000af604 00000000 00000000 myapplication!madExcept.SetLastException+0x66

STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  myapplication!System.SysUtils.FmtStr+f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: myapplication

IMAGE_NAME:  myapplication.exe

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_c0000005_myapplication.exe!System.SysUtils.FmtStr

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:wrong_symbols_c0000005_myapplication.exe!system.sysutils.fmtstr

FAILURE_ID_HASH:  {1a84a830-cc7b-3835-9000-457766b72bc7}

Followup: MachineOwner
---------



yps77
 
Posts: 1
Joined: Wed Feb 22, 2017 7:17 am

Re: Audio application crashes with madExcept enabled

Postby madshi » Wed Feb 22, 2017 2:45 pm

That looks pretty weird. Right now I've no idea why this would happen, other than maybe the process being in a completely screwed up state - but then why is there no problem without madExcept?

Can you try with the latest beta build, just to be safe?

http://madshi.net/madCollectionBeta.exe
madshi
Site Admin
 
Posts: 9311
Joined: Sun Mar 21, 2004 5:25 pm


Return to madExcept

Who is online

Users browsing this forum: No registered users and 2 guests