first-chance-exception

A C++ project I'm working on terminates upon throwing a first-chance exception. This occurs in Visual Studio 2008 in Debug mode when I first try to access a map<pair<int,int>, int> which contains a single key-value pair. There is nothing logically wrong with the code. I've read up on first-chance exceptions and understand they may not always be problematic. Nonetheless I tried breaking at all such exceptions, and as expected found several are generated which cause no issue. The class I'm working on is very large and contains many custom memory allocations. I surmise that somehow one of these

Whenever I try to debug my Windows Phone 7 C# app, I get the following message in the Output window: A first chance exception of type 'System.OverflowException' occurred in mscorlib.dll A first chance exception of type 'System.OverflowException' occurred in mscorlib.dll A first chance exception of type 'System.InvalidOperationException' occurred in Microsoft.Phone.dll ...And then, App.xaml.cs opens up in VS (still in debug mode, where I can't edit anything), and "System.Diagnostics.Debugger.Break();" is highlighted. Why is this happening, how can I fix it, and how can I prevent it in the

This is probably unrealistic, but would it be possible to enable a component to be notified of all first chance exceptions occuring in its process? We have some third-party (contracted by us) components which fail to do anything but eat excepitions and the politics of the business relationship make the whole ordeal a royal pain. We also are aware that some of our code is performing the disappointing action of letting exceptions vanish into the abyss rather than using our centralized exception logger. I assume our application would have to be started as a child process of a debugging