PDA

View Full Version : First-chance exception



sohrab
January 18, 2005, 08:56:21
Whenever i am trying to add the Montivision filters in my graph i find this message in my VC++ 6.0 Debug window my application name is DV2WMV


*First-chance exception in DV2WMV.exe: 0xC0000005: Access Violation.*


What could be the reason and how i can remove this problem

Thanks in adv

Sohrab

Marc Cymontkowski
January 20, 2005, 08:51:48
Hi Sohrab,

Please debug into the code to see at which position and for this call the exception occurs. Without detailed information i can'thelp at all.


Best Regards,

Marc Cymontkowski

sohrab
January 24, 2005, 07:08:18
Hi

When ever i use any interface related to any MV filter i get first chance excpetion in debug mode although code keep running fine..

here is my sample code when MVDeInterlace Instance is create i get that exception . In the last you will find debug report.


CoInitializeEx(NULL, COINIT_MULTITHREADED);
hr = CoCreateInstance(CLSID_FilterGraph, NULL,
CLSCTX_INPROC_SERVER, IID_IGraphBuilder, (void **)&pGraph);

CoCreateInstance(CLSID_MVDeInterlace, 0, CLSCTX_INPROC_SERVER,
IID_IBaseFilter, reinterpret_cast<void**>(&pF));



Debug Report for Last line of the code

Loaded 'C:\Program Files\MontiVision\MontiVision Development Kit\bin\filter\deinterlace.ax', no matching symbolic information found.
Loaded 'C:\WINNT\system32\ipl.dll', no matching symbolic information found.
Loaded 'C:\WINNT\system32\version.dll', no matching symbolic information found.
Loaded 'C:\WINNT\system32\lz32.dll', no matching symbolic information found.
Loaded 'C:\WINNT\system32\mfc70.dll', no matching symbolic information found.
Loaded 'C:\WINNT\system32\msvcr70.dll', no matching symbolic information found.
Loaded 'C:\WINNT\system32\oleacc.dll', no matching symbolic information found.
Loaded 'C:\WINNT\system32\shlwapi.dll', no matching symbolic information found.
Loaded 'C:\WINNT\system32\iplw7.dll', no matching symbolic information found.
Loaded 'C:\WINNT\system32\wsock32.dll', no matching symbolic information found.
Loaded 'C:\WINNT\system32\ws2_32.dll', no matching symbolic information found.
Loaded 'C:\WINNT\system32\ws2help.dll', no matching symbolic information found.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.
First-chance exception in 1.exe: 0xC0000005: Access Violation.

Bernd Peretzke
January 24, 2005, 15:34:32
Hi,

First-chance exceptions outputs are a normal behaviour from the debugger. The exception handling calls the default first chance exeption hander from the debugger. This handler throws the exception to the next exception handler and so on. An Exception isn't an error if there is a last-chance exception handler. There were often used for normal flow control. If a Software uses exceptions the debugger outputs these messages for every thrown exception.

Regards
Bernd Peretzke

brow0833
September 21, 2006, 16:29:58
Hello,

I've noticed very similar events in my program. When I start one camera with the IP Source filter in the debugger all is well. When I start the second camera my CPUs get to near 100% and I get many (100s per second) of these messages:

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

This afternoon I'll be testing a release version and will look for the spike in the CPUs.

In my simple test program that shows this behavior I'm not using and try/catch blocks.

Please advise,

Andy