Re: First-Chance exception in dlg.exe

From: Oleg Starodumov (oleg_staro_at_hotmail.com)
Date: 07/28/04


Date: Wed, 28 Jul 2004 11:17:11 +0300


> When I debug it in single step mode,the first,the second ,the third ippsMalloc goes well.
> When the fourth ippsMalloc works,the debugger generate the dialog "First-Chance
> exception in dlg.exe:0xC0000005:Access Violation.".

Close the dialog (if you use VS.NET, choose "Break") and check the code that
has thrown the exception. If it is your code, see if the exception is expected in that place.

If it is a 3rd-party code:

Let the application continue (e.g. F5, and answer "Yes" if asked to pass the exception
to the application) and see if the debugger will stop on a second-chance exception.
If it will, then there is a problem (unhandled exception) in the application (either in the library,
or in the application itself). Then again close the dialog and inspect the code
to find the reason of the unhandled exception.

If there is no second-chance exception, it means that the exception was handled
and most probably expected, so it is most likely an implementation detail
of the library.

Regards,
Oleg



Relevant Pages

  • [NT] PNG (Portable Network Graphics) Deflate Heap Corruption Vulnerability (Windows)
    ... Beyond Security would like to welcome Tiscali World Online ... exception filter, overwriting the pointer to the handler with the address ... is set to the address of the unhandled exception filter hook. ...
    (Securiteam)
  • Function names for managed callstack under SOS debugging of .NET 2.0 app
    ... wrote that sets the unhandled exception filter ... unhandled exception filter, and we generate a mini-dump. ... The callstack above happens ...
    (microsoft.public.vsnet.debugging)
  • Re: Session StageVariables
    ... I did read an article about these Unhandle Exceptions that said go to VS Options Debugging\General and uncheck Enable Just My Code, this keeps the Unhandled exception from happening when in Debug mode, but is this just masking the problem? ... So look if you have a worker threads and enclose them into try.. ... We have a base page that gets called on every page and checks for session variables. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Exceptions Thrown in Background Threads
    ... The only time where it is not practical is when the exception actually ... ought not to be in a UE handler. ... One of the fields in the unhandled exception ... app immediately thereafter - the app has no control over this. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: SEHException at app startup
    ... Droopy wrote in ... I have the same exception with this previous version so it ... > legacy code but I am not sure this is the reason why the problem ... > Unhandled exception at 0x77f410a2 in IPRRouting.exe: 0xC0000008: Un ...
    (microsoft.public.dotnet.languages.csharp)