Searching for Exception tracker engine

From: MTarvirdi (MTari_at_kosar.net)
Date: 11/28/03

  • Next message: Maris Janis Vasilevskis: "Re: D7 on W2003 server- known problems ?"
    Date: Fri, 28 Nov 2003 10:59:30 +0330
    
    

    During debugging there is many times that I get Exception and tracking the
    error and finding origin (unit/line) code is useful. this is more usefull
    specially after distribution when app get error in customer env.In
    TurboPascal days ther was a engine named "PostMortar debugger" (or like
    name) engine that when I included that with my app it reports unit/line
    information about raised error place.
    Is there any lib that I include with app to detect exception errors line no
    and trace of called methods specially can support thread env.
    Thanks
    MTarvirdi
    Mtari@kosar.net


  • Next message: Maris Janis Vasilevskis: "Re: D7 on W2003 server- known problems ?"

    Relevant Pages

    • Re: Searching for Exception tracker engine
      ... > During debugging there is many times that I get Exception and tracking the ... > error and finding origin (unit/line) code is useful. ... > name) engine that when I included that with my app it reports unit/line ...
      (borland.public.delphi.ide)
    • Custom security permission exception error message
      ... work fine *if* the app has been registered for fulltrust. ... Common Language Runtime Debugging Services ... Application has generated an exception that could not be handled. ... it gets the required privileges (unmanaged code, R/W registry ...
      (microsoft.public.dotnet.security)
    • VS 2003 IDE: How to filter specific exceptions in output window?
      ... I'm debugging a VC++ app inside Visual Studio 2003. ... At run-time my output window is polluted by numerous lines like that: ... First-chance exception at 0x00b9a99b in java.exe: 0xC0000005: Access ...
      (microsoft.public.vsnet.ide)
    • Re: Getting the default printer in 64-bit Vista
      ... Also, when debugging the app in VS.NET 2005 and I force it to quit as soon as the Exception is thrown, the Output window shows: ...
      (microsoft.public.dotnet.languages.csharp)
    • AccessViolationException after finishing debugging
      ... Attempted to read or write protected memory. ... The debugger breaks and shows some assembly code where the exception is ... this only happens while I'm debugging; ... app without debugging, no exception occurs. ...
      (microsoft.public.vsnet.debugging)