[Bug 33116] This bug prevents the game Zafehouse Diaries from running

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

Vincent Povirk  changed:

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

--- Comment #12 from Vincent Povirk  2013-04-03 15:26:23 CDT ---
Sorry, I missed your response because I didn't CC myself on the bug.

This could be related to:

converting method err:ole:CoGetClassObject class
{5a508685-a254-4fba-9b82-9a24b00306af} not registered
err:ole:CoGetClassObject no class object {5a508685-a254-4fba-9b82-9a24b00306af}
could be created for context 0x1

and

[00000009:] EXCEPTION handling: SlimDX.XAudio2.XAudio2Exception:
REGDB_E_CLASSNOTREG: Class not registered (-2147221164)

Try running: winetricks xact

Unfortunately, I can't find that class on my Windows box, so I'm not really
sure where it's supposed to come from. If you have this program installed on a
Windows machine, check if you have "{5a508685-a254-4fba-9b82-9a24b00306af}"
under HKEY_CLASSES_ROOT\CLSID.

The reason I asked for a log and a backtrace from the same run was so that I
could use the log to identify the methods in the backtrace.

You'll notice the backtrace has lines like this:

1 0x09e5c598 (0x0033f5f8)
  2 0x09e5bc48 (0x0033f6c8)
  3 0x00bab2e8 (0x0033f728)

The addresses that look like 0x09e5c598 are native (x86) code that was
translated by Mono from .NET code. Setting "WINE_MONO_VERBOSE=1" causes mono to
output lines like "Method string:.cctor () emitted at 00B111F8 to 00B1125B"
when it does this. By finding the line in the log that has a range containing
the addresses in the backtrace, I can tell which methods are involved in the
crash.

But the addresses change every time you run the program, so this only works if
both files were generated at the same time.

(Ideally, wine would be able to identify the methods on its own and put their
names in the backtrace, but setting that up properly is a big job.)

That said, I think the issue involving XAudio2 is probably at fault here, so
this information probably won't be needed.