search

Playermet / codegoogle.tart

Automatically exported from code.google.com/p/tart
0 stars 0 forks source link

Figure out how to record exception backtraces #20

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Generating exception backtraces is normally quite expensive as it involves 
walking up the stack and creating an object for each stack frame. However, the 
Tart compiler has an annotation on a catch block which allows the programmer to 
specify whether or not they need a backtrace. The default is to not generate a 
backtrace.

Some work on this has already been done - the exception personality routine 
knows whether or not a backtrace has been requested. Two difficult challenges 
remain - translating the frame address pointer into a human-readable string, 
and coordinating with the garbage collector to allocate the stack frame objects 
on the heap.

Original issue reported on code.google.com by viri...@gmail.com on 1 Mar 2011 at 10:29