From: Rich Morin <rdm@cfcl.com>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] SDB debugger
Date: Sun, 3 May 2020 09:16:58 -0700 [thread overview]
Message-ID: <7A8D26C8-67DB-4676-92D1-7842209F1807@cfcl.com> (raw)
In-Reply-To: <20200502174518.GC30768@mcvoy.com>
> On May 2, 2020, at 10:45, Larry McVoy <lm@mcvoy.com> wrote:
>
> ... But truth be known, I'm sort of a printf() debugger. ...
So am I, and ISTR Brian Kernighan and Larry Wall saying that they are, as well. Over the years, I've written some scripts to make this less painful. For example, in Ruby, I use the et() script, as written up in http://wiki.cfcl.com/Projects/Ruby/Phone_Home:
l = %w[ context~ dir_path# file_path foo.bar bar[:baz] ]
et(l)
This produces the following output:
some_script:72:in `main'
context { :foo => "yada yada yada", ... }
file_path "a/b/c"
foo.bar :warn
bar[:baz] 42
I also have a tiny Elixir script, ii/2, which works nicely in pipelines:
...
|> ii(:foo)
...
-r
next prev parent reply other threads:[~2020-05-03 16:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 2:52 Doug McIlroy
2020-05-02 17:45 ` Larry McVoy
2020-05-03 16:16 ` Rich Morin [this message]
2020-05-12 4:36 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2020-05-03 2:21 Norman Wilson
2020-05-03 2:41 ` Larry McVoy
2020-05-03 7:14 ` arnold
2020-05-03 3:05 ` Rob Pike
2020-05-01 20:48 Paul Ruizendaal
2020-05-01 21:57 ` Clem Cole
2020-05-02 9:10 ` Paul Ruizendaal
2020-05-02 16:04 ` Clem Cole
2020-05-01 23:05 ` Jeremy C. Reed
2020-05-02 0:49 ` Noel Hunt
2020-05-02 1:22 ` Rob Pike
2020-05-02 3:49 ` Noel Hunt
2020-05-02 20:16 ` Paul Ruizendaal
2020-05-03 6:58 ` arnold
2020-05-03 16:13 ` Clem Cole
2020-05-03 16:53 ` Henry Bent
2020-05-03 17:06 ` Henry Bent
2020-05-03 17:13 ` Henry Bent
2020-05-03 20:26 ` Clem Cole
2020-05-03 17:35 ` Paul Winalski
2020-05-03 21:27 ` Paul Ruizendaal
2020-05-12 4:15 ` Dave Horsfall
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=7A8D26C8-67DB-4676-92D1-7842209F1807@cfcl.com \
--to=rdm@cfcl.com \
--cc=tuhs@tuhs.org \
/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).