From: David Leimbach <leimy2k@icloud.com>
To: 9front@9front.org
Cc: igor@9lab.org
Subject: Re: [9front] Howto: debugging with acid(1)
Date: Wed, 13 Oct 2021 18:32:27 -0400 [thread overview]
Message-ID: <BE3E8036-3C85-4E7C-B00C-D9F841F04EA0@icloud.com> (raw)
In-Reply-To: <152CB01EF1336EFA68ACDD6BE6726AA6@9lab.org>
Very nice! I struggled with acid on my raspberry pi! This is cool!
Sent from my iPad
> On Oct 13, 2021, at 11:19 AM, igor@9lab.org wrote:
>
> Finally I organised my scattered notes on debugging with acid(1)
> and put it together into a howto with screencast:
>
> * https://9lab.org/plan9/debugging-with-acid/
>
> Experienced hackers most likely already know everything that is
> shown. If you haven't used acid(1) before for debugging, or it
> has been a while and you forgot, this will hopefully get you
> started quickly...
>
> If you find any issues please let me know.
>
> HTH
>
> Cheers,
> Igor
>
next prev parent reply other threads:[~2021-10-13 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 15:11 igor
2021-10-13 22:32 ` David Leimbach [this message]
2021-10-14 19:34 ` qwx
2021-10-15 11:45 ` igor
2021-10-15 14:06 ` Stuart Morrow
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=BE3E8036-3C85-4E7C-B00C-D9F841F04EA0@icloud.com \
--to=leimy2k@icloud.com \
--cc=9front@9front.org \
--cc=igor@9lab.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).