On Sun, Nov 4, 2012 at 11:26 PM, Alexandre Oliva <aol...@redhat.com> wrote: > On Nov 1, 2012, Dehao Chen <de...@google.com> wrote: > >> I see your point. How about we guard these changes with a flag, say >> -gless-jumpy > > The right (DWARF-expected) approach to avoid this sortof jumpiness is to > teach GCC to emit .locs with is_stmt=1, along the lines (and > limitations) described in my GCC Summit paper on stmt frontier notes, > that proposes further extensions to deal with the foreseen limitations.
Right. gdb could also instead of show a single line (and that changing all the time) show all currently "active" lines (thus scan the current function for lines that appear and compute their "liveness"). A step would then jump to the next stmt that changes line liveness. Richard. > http://people.redhat.com/~aoliva/papers/sfn/gcc2010.pdf > > -- > Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/ > You must be the change you wish to see in the world. -- Gandhi > Be Free! -- http://FSFLA.org/ FSF Latin America board member > Free Software Evangelist Red Hat Brazil Compiler Engineer
