Just pulling things back together here: On Thu 03 Dec 2009 23:52, Neil Jerram <n...@ossau.uklinux.net> writes:
> Neil Jerram <n...@ossau.uklinux.net> writes: > >> [...] wondering whether and how we >> will provide similar debugging facilities for compiled code as we have >> in 1.8.x for interpreted code. > > Some more thoughts here, to try to build a complete new picture. > > Things that we can do quite nicely in 1.8.x are: > - stack inspection > - seeing the frames and what is happening, for context > - mapping back to source code > - querying variable values > - evaluating an expression in a frame's local environment > - breakpoints > - tracing > - single stepping. > > We should try to include profiling and code coverage in the picture. We can do all this in 1.9/2.0 now, except breakpoints and single stepping, and evaluating in the context of a frame isn't accessible right now. I want to fix the breakpoints and stepping situation soonish, though. Andy -- http://wingolog.org/
