Avconv found invalid data processing input

Exception class

definition

Represents errors that occur during application execution.

Inheritance
Derived
Attributes
Implemented

Examples

The following example demonstrates a block that is defined to handle ArithmeticException errors This block also catches DivideByZeroException errors, because DivideByZeroException derives from ArithmeticException and there is no block explicitly defined for DivideByZeroException errors.

Hints

This class is the base class for all exceptions. When an error occurs, the system or the currently running application will notify you by throwing an exception that contains information about the error. Either the system or the currently executing application reports it by throwing an exception that contains information about the error. After an exception is thrown, it is handled by the application or by the default exception handler.

Content of this section: In this section:

Errors and exceptions
Try / catch blocks
Exception type features
Exception class properties
Performance considerations
Re-throwing an exception
Choosing standard exceptions
Implementing custom exceptions

Errors and exceptions

Run-time errors can occur for a variety of reasons. However, not all errors should be handled as exceptions in your code Here are some categories of errors that can occur at run time and the appropriate ways to respond to them.

  • Usage errors.Usage errors.A usage error represents an error in program logic that can result in an exception. However, the error should not be fixed by exception handling, but by changing the faulty one Codes.However, the error should be addressed not through exception handling but by modifying the faulty code. b. Assumes that the argument must always be non-null. For example, the override of the Object.Equals (Object) method in the following example assumes that the argument must always be non-null.

    The NullReferenceException exception that throws when the value can be cleared by modifying the source code so that it is explicitly checked before calling the Object.Equals override and then recompiled. The NullReferenceException exception that results when is can be eliminated by modifying the source code to explicitly test for null before calling the Object.Equals override and then re-compiling.The following example contains the corrected source code that handles a argument.