VS 2003 IDE: How to filter specific exceptions in output window?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I'm debugging a VC++ app inside Visual Studio 2003. The app also uses
Sun's JDK / JNI.

At run-time my output window is polluted by numerous lines like that:

First-chance exception at 0x00b9a99b in java.exe: 0xC0000005: Access
violation reading location 0x00000000.

I already found out that surprisingly Sun writes "[Java] uses access
violations for internal communication. It's not unusual to see this in
the Windows debugger". Sounds unusual, but I have to live with it

I'm already ignoring this exception using the VS exception dialog, but
this does not stop the spill onto my output window.

How do I achieve that this specific exception is not printed in my
output window where between the endless lines of crap it may hide real
problems?

Any help appreciated.

.

Relevant Pages

  • 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 ... Is there any lib that I include with app to detect exception errors line no ...
    (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)
  • 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)
  • Re: 64b Windows - crashes not detected
    ... RoomTest testRoom; ... Crash is right there at 01112528. ... First-chance exception at 0x01112528 in crashTest.exe: 0xC0000005: ... see one AV trace in your output window at every call to OnDraw (e.g. ...
    (microsoft.public.vc.mfc)