ok, read this again and i see that you want to avoid all the intermediate
prints from next(). i looked at /sys/lib/acid/port but can't see where the
print is happening; maybe it's deeper in builtins.
something like this, but with better housekeeping to work with existing
acid code, could work:
defn Next() {
printto("/env/nextStmt", pcfile(*PC),":",pcline(*PC)+1);
bpset(filepc(readfile("/env/nextStmt")));
cont();
}
On Thu, Nov 7, 2013 at 11:40 PM, Skip Tavakkolian <
[email protected]> wrote:
> Isn't step what you're looking for?
>
> > On Nov 7, 2013, at 6:46 PM, Nick Owens <[email protected]> wrote:
> >
> > 9fans,
> >
> > i find myself needing to use acid a lot lately, and maybe i am going
> > about it wrong. i very much dislike that when i next() in acid, acid
> > will step through every subcall. what i would like is that it would
> > instead behave more like gdb's next. is this crazy or am i going about
> > using acid wrong?
> >
> > maybe someone has acid analogues of gdb's next, finish, until as
> > described here.
> >
> > https://sourceware.org/gdb/onlinedocs/gdb/Continuing-and-Stepping.html
> >
> > nick
> >
>
