9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Nick Owens <mischief@9.offblast.org>
To: 9fans@9fans.net
Subject: [9fans] acid analogues of gdb stepping commands
Date: Thu,  7 Nov 2013 18:46:00 -0800	[thread overview]
Message-ID: <20131108024600.GN11218@iota.offblast.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 479 bytes --]

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


[-- Attachment #2: Type: application/pgp-signature, Size: 851 bytes --]

             reply	other threads:[~2013-11-08  2:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  2:46 Nick Owens [this message]
2013-11-08  7:40 ` Skip Tavakkolian
2013-11-08 10:03   ` Skip Tavakkolian
2013-11-08 23:46     ` Nick Owens
2013-11-08 23:51       ` erik quanstrom
2013-11-09  0:36         ` Nick Owens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131108024600.GN11218@iota.offblast.org \
    --to=mischief@9.offblast.org \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).