about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2017-11-01 02:51:23 -0700
committerKartik K. Agaram <vc@akkartik.com>2017-11-01 02:51:23 -0700
commita6fe8e274683c14efc6585b1b566afe9abfea7d1 (patch)
tree53e2c22fd0edfceee075c83b5527e0d211928298
parentdba9f1359dd720863cd6a1acd0646a090169de6b (diff)
downloadmu-a6fe8e274683c14efc6585b1b566afe9abfea7d1.tar.gz
4101
-rw-r--r--034address.cc4
1 files changed, 2 insertions, 2 deletions
diff --git a/034address.cc b/034address.cc
index 266580a1..6e33279c 100644
--- a/034address.cc
+++ b/034address.cc
@@ -33,8 +33,8 @@
 //:   b) If you allow data to be reclaimed, you have to be careful not to
 //:   leave any stale addresses pointing at it. Otherwise your program might
 //:   try to lookup such an address and find something unexpected. Such
-//:   problems can be very hard to track down, and they can also be exploited
-//:   to break into your computer over the network, etc.
+//:   "memory corruption" problems can be very hard to track down, and they
+//:   can also be exploited to break into your computer over the network, etc.
 //:
 //: To avoid these problems, we introduce the notion of a *reference count* or
 //: refcount. The life cycle of a bit of data accessed through addresses looks