The Include managed methods option and the Include native methods in the session settings can be used to exclude certain methods and functions from the call stack. For more information about these settings, see Call Stacks Settings Page.
If a function is excluded from a call stack, it is replaced with an entry named [Skipped frame(s)]. If two or more adjacent functions are skipped, only one [Skipped frame(s)] entry will be added, which will cause the stack depth to be decreased.
One drawback of using the Include managed methods and the Include native methods options is that it will significantly reduce the call stack information available for framework methods, OS functions, and third party components, making it harder to identify how managed memory and unmanaged resources are used. A better option is usually to include All managed method and native functions, and use the Call Stack Reducer to exclude "unimportant" methods and functions. Unless manual control over call stack reduction is needed, it is recommended that the Call Stack Reducer is used.