. . . . . . . . . . . . . . . . . . . . . . . . . 446 34 Stack Traces 448 34.1 Viewing a stack trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 34.2 Extracting useful information were to profile dumbsum3, and a backtrace was taken while it was executing dumbsum(1), the back- trace would look like this: dumbsum3 dumbsum(3) dumbsum(2) dumbsum(1) Consequently, this child function Julia 1.8 This functionality requires at least Julia 1.8. The allocation profiler records the stack trace, type, and size of each allocation while it is running. It can be invoked with Profile.Allocs.@profile

. . . . . . . . . . . . . . . . . . . . . . . . . 445 34 Stack Traces 447 34.1 Viewing a stack trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 34.2 Extracting useful information were to profile dumbsum3, and a backtrace was taken while it was executing dumbsum(1), the back- trace would look like this: dumbsum3 dumbsum(3) dumbsum(2) dumbsum(1) Consequently, this child function Julia 1.8 This functionality requires at least Julia 1.8. The allocation profiler records the stack trace, type, and size of each allocation while it is running. It can be invoked with Profile.Allocs.@profile

. . . . . . . . . . . . . . . . . . . . . . . . . 445 34 Stack Traces 447 34.1 Viewing a stack trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 34.2 Extracting useful information were to profile dumbsum3, and a backtrace was taken while it was executing dumbsum(1), the back- trace would look like this: dumbsum3 dumbsum(3) dumbsum(2) dumbsum(1) Consequently, this child function Julia 1.8 This functionality requires at least Julia 1.8. The allocation profiler records the stack trace, type, and size of each allocation while it is running. It can be invoked with Profile.Allocs.@profile

. . . . . . . . . . . . . . . . . . . . . . . . . 445 34 Stack Traces 447 34.1 Viewing a stack trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 34.2 Extracting useful information were to profile dumbsum3, and a backtrace was taken while it was executing dumbsum(1), the back- trace would look like this: dumbsum3 dumbsum(3) dumbsum(2) dumbsum(1) Consequently, this child function Julia 1.8 This functionality requires at least Julia 1.8. The allocation profiler records the stack trace, type, and size of each allocation while it is running. It can be invoked with Profile.Allocs.@profile

. . . . . . . . . . . . . . . . . . . . . . . . . 445 34 Stack Traces 447 34.1 Viewing a stack trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 34.2 Extracting useful information were to profile dumbsum3, and a backtrace was taken while it was executing dumbsum(1), the back- trace would look like this: dumbsum3 dumbsum(3) dumbsum(2) dumbsum(1) Consequently, this child function Julia 1.8 This functionality requires at least Julia 1.8. The allocation profiler records the stack trace, type, and size of each allocation while it is running. It can be invoked with Profile.Allocs.@profile

responsible for the call. If it fails, the IOLoop will log a stack trace: # The IOLoop will catch the exception and print a stack trace in # the logs. Note that this doesn't look like a normal call, since specified status code; all other exceptions return a 500 status. The default error page includes a stack trace in debug mode and a one-line description of the error (e.g. “500: Internal Server Error”) otherwise serve_traceback=True: When an exception in a RequestHandler is not caught, an error page including a stack trace will be generated. Autoreload mode is not compatible with the multi-process mode of HTTPServer. You

responsible for the call. If it fails, the IOLoop will log a stack trace: # The IOLoop will catch the exception and print a stack trace in # the logs. Note that this doesn't look like a normal call, since specified status code; all other exceptions return a 500 status. The default error page includes a stack trace in debug mode and a one-line description of the error (e.g. “500: Internal Server Error”) otherwise serve_traceback=True: When an exception in a RequestHandler is not caught, an error page including a stack trace will be generated. Autoreload mode is not compatible with the multi-process mode of HTTPServer. You

. . . . . . . . . . . . . . . . . . . . . . . . . 435 34 Stack Traces 437 34.1 Viewing a stack trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 34.2 Extracting useful information were to profile dumbsum3, and a backtrace was taken while it was executing dumbsum(1), the back- trace would look like this: dumbsum3 dumbsum(3) dumbsum(2) dumbsum(1) Consequently, this child function Julia 1.8 This functionality requires at least Julia 1.8. The allocation profiler records the stack trace, type, and size of each allocation while it is running. It can be invoked with Profile.Allocs.@profile

. . . . . . . . . . . . . . . . . . . . . . . . . 435 34 Stack Traces 437 34.1 Viewing a stack trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 34.2 Extracting useful information were to profile dumbsum3, and a backtrace was taken while it was executing dumbsum(1), the back- trace would look like this: dumbsum3 dumbsum(3) dumbsum(2) dumbsum(1) Consequently, this child function Julia 1.8 This functionality requires at least Julia 1.8. The allocation profiler records the stack trace, type, and size of each allocation while it is running. It can be invoked with Profile.Allocs.@profile

. . . . . . . . . . . . . . . . . . . . . . . . . 435 34 Stack Traces 437 34.1 Viewing a stack trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 34.2 Extracting useful information were to profile dumbsum3, and a backtrace was taken while it was executing dumbsum(1), the back- trace would look like this: dumbsum3 dumbsum(3) dumbsum(2) dumbsum(1) Consequently, this child function Julia 1.8 This functionality requires at least Julia 1.8. The allocation profiler records the stack trace, type, and size of each allocation while it is running. It can be invoked with Profile.Allocs.@profile