From: tih at hamartun.priv.no (Tom Ivar Helbekkmo)
Subject: [COFF] Monitoring by loudspeaker
Date: Sun, 23 Aug 2020 10:58:19 +0200 [thread overview]
Message-ID: <m27dtpu4b8.fsf@thuvia.hamartun.priv.no> (raw)
In-Reply-To: <20200712145822.GA72854@fuz.su> (Robert Clausecker's message of "Sun, 12 Jul 2020 16:58:22 +0200")
Robert Clausecker <fuz at fuz.su> writes:
> When the computer is in a tight endless loop, the accumulator takes the
> same series of values every time it's in the loop. Thus, instead of
> white noise you get a sound whose frequency is the clock frequency of
> the machine divided by the number of cycles spent by one loop iteration.
A buddy and I did something somewhat related back in the early eighties,
when we were teaching ourselves programming, using, among other things,
his Tandy TRS-80 home computer. We discovered that a cheap "transistor
radio", sitting close to the computer, would be affected by the noise
generated by it, and then we figured out that if we didn't tune it to a
radio station, we'd get only the noise. Leaving that on as we worked on
a program, we got familiar with the sound of the code, and became able
to follow the execution by the changing patterns -- and if it did get
stuck in a loop somewhere, we'd not only hear it, but we would also have
a pretty good idea where it happened.
-tih
--
Most people who graduate with CS degrees don't understand the significance
of Lisp. Lisp is the most important idea in computer science. --Alan Kay
prev parent reply other threads:[~2020-08-23 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200711203020.GA1884@minnie.tuhs.org>
[not found] ` <202007120222.06C2MtdJ140032@tahoe.cs.Dartmouth.EDU>
2020-07-12 11:58 ` [COFF] [TUHS] Monitoring by loudspeaker (was: BTL pranks)
2020-07-12 13:25 ` crossd
2020-07-12 14:58 ` fuz
2020-08-23 8:58 ` tih [this message]
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=m27dtpu4b8.fsf@thuvia.hamartun.priv.no \
--to=coff@minnie.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).