Hey guys.

Is it possible to have foobar2000 disable the creation of crash reports when debugging a component?

Reason I ask is that I have been working on a DSP component for a while (hoping to get it stable enough so other people can try it) and I get crash reports sometimes. I know exactly the conditions in which the crash happens, but its annoying that FB2Ks exception hander always kicks in when debugging sometimes, especially when working to fix the bugs.

So, is there anything in FB2K to disable such reports (or just writing to failure.txt like in the past)? Its just I don't want to accidently submit online a crash report when I know exactly the conditions it crashes and it can be tedious doing this all the time when debugging.

thanks.

You should debug it in a debugger, the "problem" would go away.

Heh, I know you would say something like that, I admire your wit

Though it is tedious when trialing a reverb algo and you find FB2K crashing because of the filter (plus things that deal with the complete lack of clipping reduction), and then you deal with all the error reports.

Well, I guess thats a perfect alternative, considering I know how to fully well use a debugger, usermode and kernel mode ones included.

I guess you could dump this in the Recycle Bin then.

Well it's just so much simpler to run debug builds directly from MSVC IDE and break to the faulty code line immediately instead of guessing or determining the crash location from the crashlog stack trace. Together with OutputDebugString()/uDebugLog(), debug CRT, etc. I can't think of any reason why one wouldn't want to do that.

Touché. I guess then I better use the MSVC IDE more (in my projects, I hardly use it at all).
Well, I guess it makes this thread redundant

Thanks for the debugging tips anyway