![]() ![]() The index range for each category of filters can be found from the SpecificEvents, SpecificExceptions, and ArbitraryExceptions values returned by GetNumberEventFilters, as described in the following table: Event Filters The index is a number between zero and one less than the total number of filters (inclusive). If the output is not known, it is considered a match.Įach event filter has an index. The argument uses the string wildcard syntax and is compared with the debug output from the target. The argument is an expression that is evaluated by the engine when the argument is set. If the name of the module or process is not available, it is considered a match. The argument uses the string wildcard syntax and is compared with the image name (ignoring path) when the event occurs. The debug output from the target must match the argument.3 The base address of the unloaded module must be the same as the argument.2 The name of the loaded module must match the argument.1 The name of the exited process must match the argument.1 The name of the created process must match the argument.1 The following table lists the event filters that take arguments and how they restrict the events which match them: Event If a specific filter has no argument, there is no restriction on which events it matches. GetSpecificFilterArgument and SetSpecificFilterArgument will get and set arguments for those specific filters which support arguments. Some specific filters take arguments that restrict which events the filter matches. SetExceptionFilterParameters can also be used to add and remove arbitrary exception filters.Ī short description of specific filters is returned by GetEventFilterText. The break status and handling status for event filters can be set using SetSpecificFilterParameters and SetExceptionFilterParameters. The parameters for specific event filters and exception filters are returned by GetSpecificFilterParameters and GetExceptionFilterParameters. To get and set the second-chance command, use GetExceptionFilterSecondCommand and SetExceptionSecondChanceCommand. A separate second-chance command can be executed upon the second-chance exception event. For exception filters, this command is executed on the first-chance of the exception. GetEventFilterCommand and SetEventFilterCommand can be used to get and set this command. This command is executed by the engine when an event matching the filter occurs. Commands and ParametersĮvent filters can have a debugger command associated with them. #Computercraft multi event filter code#If there is no exception filter with the same exception code as the exception event, the exception event will be handled by the default exception filter. Some event filters have an additional parameter which further restricts the events they match.Īn exception event matches an exception filter if the exception code for the exception event is the same as the exception code for the exception filter. The number of filters in each category is returned by GetNumberEventFilters.Īn event matches a specific event filter if the type of the event is the same as the type of the filter. The filters in categories 1 and 2 are collectively known as specific filters, and the filters in categories 2 and 3 are collectively known as exception filters. These are filters for exception events that have been added manually. See Specific Exceptions for a list of the specific exception filters.Īrbitrary exception filters. The rest are filters for those exceptions for which the engine has built-in filters. The first specific exception filter is the default exception filter. See DEBUG_FILTER_XXX for a list of these events. These are the filters for all the non-exception events. Note If more sophisticated event filtering is required, event callbacks can be used.Įvent filters are divided into three categories. ![]() If the event is an exception event, the handling status determines whether the exception should be considered handled or not-handled in the target. If it does, the break status for the event filter influences whether the debugger will break into the target. When an event occurs, the engine determines whether that event matches an event filter. Event filters provide simple event filtering they influence how the debugger engine proceeds after an event occurs in a target. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |