Rename event-horizon to error-limit; the former may have trendy black-hole
associations, but the latter actually cues one to what it might achieve.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@418 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/coregrind/vg_errcontext.c b/coregrind/vg_errcontext.c
index 60eaba0..46838b6 100644
--- a/coregrind/vg_errcontext.c
+++ b/coregrind/vg_errcontext.c
@@ -497,7 +497,7 @@
the burden of the error-management system becoming excessive in
extremely buggy programs, although it does make it pretty
pointless to continue the Valgrind run after this point. */
- if (VG_(clo_event_horizon)
+ if (VG_(clo_error_limit)
&& (vg_n_errs_shown >= M_VG_COLLECT_NO_ERRORS_AFTER_SHOWN
|| vg_n_errs_found >= M_VG_COLLECT_NO_ERRORS_AFTER_FOUND)) {
if (!stopping_message) {
@@ -518,7 +518,7 @@
VG_(message)(Vg_UserMsg,
"Final error counts will be inaccurate. Go fix your program!");
VG_(message)(Vg_UserMsg,
- "Rerun with --event-horizon=no to disable this cutoff. Note");
+ "Rerun with --error-limit=no to disable this cutoff. Note");
VG_(message)(Vg_UserMsg,
"that your program may now segfault without prior warning from");
VG_(message)(Vg_UserMsg,