0
0

Hello,
I’m trying to package a xbox 360 live arcade title, and we have a crash using xbWatson while initializing FModEx (using xbWatson is part of the process for Microsoft to validate a submission).

I tried to compiled with both fmodex 4.04.14 or fmodex 4.04.28, and it crashes the same way on each thread initialization (I use July 2006 Xbox360 SDK).

I try to use xbWatson on any of the FModEx samples and it does the same.
Here is a short snipset of what xbWatson says when launching playsound sample :

[code:1mv5kshg]
FMOD: SystemI::close : done.
FMOD: Thread::initThread : Initializing FMOD XMP GetStatus thread. priority -1
FMOD: Thread::initThread : – Stacksize 0. Stack pointer 00000000 : usesemaphore = 1 : sleeptime = 0
Exception : 4177526784 1080890248 2148030864 FirstChance
[/code:1mv5kshg]

If I press continue, it told me [code:1mv5kshg]FMOD: Thread::initThread : done.[/code:1mv5kshg] and the program runs fine (except xbWatson reports 3 more exceptions).

Any hint on what it could be ? (xbWatson bug on thread ? wrong sdk version ?)
Thanks

  • You must to post comments
0
0

I suggest updating to the latest FMOD version and also the latest XDX version first. If this doesn’t resolve the issue please write to support@fmod.org as we can’t discuss console platform details here.

  • You must to post comments
0
0

This is not a crash it is a purposeful exception thrown by the application to name the thread in debug mode so that it shows up in the debugger. It only appears to be caught in watson anyway.

Just use the latest release version of fmod where it is ifdef’ed out for the release build.

  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.