Debugging an appcrash

[imilne]

This is what I get for not programming for months

Code:

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    NextPVR.exe
  Application Version:    1.0.0.0
  Application Timestamp:    54553dc4
  Fault Module Name:    MediaInfo.dll
  Fault Module Version:    0.7.72.0
  Fault Module Timestamp:    54ad43f3
  Exception Code:    c00000fd
  Exception Offset:    002b0e47
  OS Version:    6.1.7601.2.1.0.256.4
  Locale ID:    2057
  Additional Information 1:    4f6e
  Additional Information 2:    4f6e33d09ad919737f34aa7adcec3ad4
  Additional Information 3:    afc5
  Additional Information 4:    afc52a5f0f7a29752a855fef86ccb0bb

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I've tracked down the line that causes the error, but is there any way to get more information about what might be going wrong? I know nothing about 'proper' debugging with C#, but this is fairly simple stuff (in terms of usage of the MediaInfo DLL), and happens when trying to use a newer version of the DLL with my existing code.

Iain

[mvallevand]

Not 100% related but maybe compare the wrapper files to the dll to see what changed?

Martin

[imilne]

Not 100% related but maybe compare the wrapper files to the dll to see what changed?

Do you mean the changelog? There's certainly a bunch of stuff changed, but nothing obvious that would break my code. It's actually crapping out on the initial Open() call to the media file so I'm not even getting as far as querying for any info on it. The strange thing is it's still working with 25fps stuff, but failing on other framerates.

There was also a slightly updated MediaInfoDLL.cs file (that gets chucked into the project) but including that hasn't helped. Its changes were minimal.

Iain

[whurlston]

Are you launching NextPVR from Visual Studio debug or are you building your plugin then manually launching NextPVR?

[imilne]

Are you launching NextPVR from Visual Studio debug or are you building your plugin then manually launching NextPVR?

I've always just done the latter (out of ignorance).

Iain

[imilne]

Hmm, I'm not seeing the options (this) suggests. Maybe it's something I can't do with just Visual Studio Express?

Iain

[whurlston]

In the project properties, select "Build" on the left and then set the "Output path:" (scroll down) to the plugin folder. This will build your plugin dll where it should be.

Select "Debug" on the left and under "Start Action" select "Launch external program" and point it to NextPVR.exe.

Right Click the project and select "Debug" -> "Start New Instance".

It should now break on errors. You can also use a try/catch statement with a breakpoint on the "catch".

[whurlston]

Never mind... looks like the express versions don't support this.

[whurlston]

Try this:

Code:

try {
    // put the problem line here
}
catch (Exception Ex) {
    Logger.Debug(Ex.Message + "\r\n" + Ex.StackTrace); // reference NPVR's logger function. I don't remember it's exact location
}

The exception should now get written to NextPVR.log

[imilne]

The exception should now get written to NextPVR.log

It was already wrapped in a try/catch, but it doesn't seem to do much catching unfortunately. Hopefully the full version of VS will offer up some clues...

Iain