RE: Disabling exception trace messages

Further information:

I have created a simple test application that I can build in VC6 and VC7 and
a tick comparison shows the following:

A current quick comparison with 5000 loops (in ticks):

In debugger
Trace: VC6 - 250, VC7 - 7734
Exceptions: VC6 - 344, VC7 - 10672

Outside debugger:
Trace: VC6 - 125, VC7 - 141
Exceptions: VC6 - 63, VC7 - 47

So it is actually 30 times slower!!!

"Lee Marmara" wrote:

> Can you tell me why this now takes so much longer than VC6? With this taking
> so long it now means that our whole development cycle is now effected as
> debug times have slowed by a factor of 10!!! Is there any way we can speed
> this up?
>
> Is this going to be improved in VC2005?
>
> ""Gary Chang[MSFT]"" wrote:
>
> > Hi Lee,
> >
> > >Some of these messages we have managed to supress
> > >using debug levels, but those from first chance exceptions
> > >still occur. These are making debugging a painful process
> > >as it is now significantly slower...
> >
> > The VS2003's debugger will break execution of the program when an exception
> > occurs, and writes an exception message to the Output window, giving you a
> > chance to debug it. You can choose whether or not you want the debugger to
> > break on a given type of exception or on a category of exceptions.
> >
> > This feature is by design in VS.NET 2003's debugger, you can change the
> > debugger's default handling exceptions configuraion in the Debug/Exceptions
> > config dialog, but I am afraid you could not suppress those exception's
> > trace messages, please refer to the following MSDN doc for the details:
> >
> > Changing How the Debugger Handles Exceptions
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/htm
> > l/vxgrfchanginghowdebuggerhandlesexceptions.asp
> >
> >
> > Thanks!
> >
> > Best regards,
> >
> > Gary Chang
> > Microsoft Community Support
> > --------------------
> > Get Secure! ¡§C www.microsoft.com/security
> > Register to Access MSDN Managed Newsgroups!
> > http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
> > &SD=msdn
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
.

Relevant Pages

  • Re: how can I create minidumps of second chance exceptions in .NET 1.1 managed code?
    ... Using the configuration like you suggested sends the exception to the JIT debugger which is registered in a system-wide manner, and I don't want to register there. ... ADPlus is usually good in catching 2nd chance managed exceptions." ...
    (microsoft.public.vsnet.debugging)
  • Re: Step by Step skips large chunks of code
    ... Do your threads throw exceptions, ... the debugger will automatically break it when an exception is thrown. ... You can send feedback directly to my manager at: ... Added SP1, the debugger started skipping within threads. ...
    (microsoft.public.vsnet.debugging)
  • Re: Mixed assembly crashes on exit
    ... (when running the app under debugger, watch also for unexpected first chance ... exceptions in Debug Output window, or configure the debugger to stop ... Also try to set breakpoint in SingletoneDomainUnload function and step ... how does the disassembly around the place of crash look? ...
    (microsoft.public.vsnet.debugging)
  • Re: Set DEBUG flag at runtime?
    ... always break on exceptions, even if there was a catch block. ... debugger to break in the place where the exceptions occur when debugging, ... DEBUG mode rather than RELEASE. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: throwing out of memory exception in c++ doesnt work
    ... >> crash is related to exhaustion of the free store! ... >> debugger you can fire up and trace through the program with? ... >that my memory is filling up until the SIGKILL interrupts. ... basically all standard exceptions derive from "exception"; ...
    (comp.lang.cpp)
Loading