lmi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [lmi] master 12537383 03/10: Remove an unuseful option


From: Greg Chicares
Subject: [lmi-commits] [lmi] master 12537383 03/10: Remove an unuseful option
Date: Wed, 8 Jun 2022 19:41:00 -0400 (EDT)

branch: master
commit 12537383b8b881a70e5758b616fba6ebaebe2c23
Author: Gregory W. Chicares <gchicares@sbcglobal.net>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Remove an unuseful option
    
    Few $UBSAN_OPTIONS settings are generally useful--perhaps only one.
    
    - UBSAN_OPTIONS=print_stacktrace=1 is generally useful. Without it, only
    a one-line diagnostic is printed, which does not indicate which program
    triggered the UB.
    
    - UBSAN_OPTIONS=print_summary=1 seems merely to print "SUMMARY" and copy
    a one-line diagnostic that would be printed anyway.
    
    - UBSAN_OPTIONS=log_path="some_path" feels like a slapdash afterthought.
    If "some_path" has a terminal '/', then output is silently discarded.
    Without a terminal '/', a log is written, but with a randomized name
    like "some_path.240247" that isn't available to scripts. The only solid
    technique for processing UBSan output in scripts is to intercept stderr.
---
 gwc/.zshrc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gwc/.zshrc b/gwc/.zshrc
index cab7617a..6f0699f6 100644
--- a/gwc/.zshrc
+++ b/gwc/.zshrc
@@ -54,8 +54,8 @@ export LESSCHARSET=utf-8
 #   https://lists.nongnu.org/archive/html/lmi/2022-06/msg00016.html
 export WINEDEBUG=-all,err+all,fixme+all
 
-# These UBSan options are generally useful.
-export UBSAN_OPTIONS=print_stacktrace=1:print_summary=1
+# This UBSan option is generally useful.
+export UBSAN_OPTIONS=print_stacktrace=1
 
 # Use vim keybindings.
 bindkey -v



reply via email to

[Prev in Thread] Current Thread [Next in Thread]